Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3037dd769ef4be67a8705c609f6b6ed405f0df4c57c43df030310fc8ef75369e

Tx prefix hash: dfb6cf520f9c9bd7e49a6d0b65df6b06cb7daeb0b0fe9291d75ea34f3e69b633
Tx public key: f55b37ce2265ab7501afa2b3be9ce548c8f631b62717d61266dd2b76854768f1
Timestamp: 1711766623 Timestamp [UCT]: 2024-03-30 02:43:43 Age [y:d:h:m:s]: 01:007:21:00:01
Block: 989313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266563 RingCT/type: yes/0
Extra: 01f55b37ce2265ab7501afa2b3be9ce548c8f631b62717d61266dd2b76854768f102110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f61f72091b47f82a524191dfc297999c0915ae97b46c21df4c49b0f80661ade0 0.600000000000 1449608 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": 989323, "vin": [ { "gen": { "height": 989313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f61f72091b47f82a524191dfc297999c0915ae97b46c21df4c49b0f80661ade0" } } ], "extra": [ 1, 245, 91, 55, 206, 34, 101, 171, 117, 1, 175, 162, 179, 190, 156, 229, 72, 200, 246, 49, 182, 39, 23, 214, 18, 102, 221, 43, 118, 133, 71, 104, 241, 2, 17, 0, 0, 0, 9, 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