Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: dd46f1099d734faa182bc9a27c8daca84d8472311dc12197f9031e200e91b1e5

Tx prefix hash: 8d1355b326c8b992ef6495dbdee2b102551f20cef3338ccf40198fa575e61aa9
Tx public key: d8f02515bb9427db0167214389771a3f5db21cd1f80a407172a956e5a9569954
Timestamp: 1712395919 Timestamp [UCT]: 2024-04-06 09:31:59 Age [y:d:h:m:s]: 01:046:22:33:49
Block: 994487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294571 RingCT/type: yes/0
Extra: 01d8f02515bb9427db0167214389771a3f5db21cd1f80a407172a956e5a956995402110000001052d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fccb1e10182c3a76afa2903acc3c1ea15e273ac2b81ff5502c325e0191ed1bf 0.600000000000 1454889 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 994497, "vin": [ { "gen": { "height": 994487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fccb1e10182c3a76afa2903acc3c1ea15e273ac2b81ff5502c325e0191ed1bf" } } ], "extra": [ 1, 216, 240, 37, 21, 187, 148, 39, 219, 1, 103, 33, 67, 137, 119, 26, 63, 93, 178, 28, 209, 248, 10, 64, 113, 114, 169, 86, 229, 169, 86, 153, 84, 2, 17, 0, 0, 0, 16, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8