Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2f5bd522af6f2a83c8007f1f8cc02bbf60657a95756cfec08e2bf991d14cbdd

Tx prefix hash: a492645d93da95ea96bb3c9e2b8dae7a199d671904795d088fc4576366df939c
Tx public key: 15f3905cda23ea81b35df55e321c072fca87f7bc0b2c0fec88f3827814ec9a0f
Timestamp: 1758789444 Timestamp [UCT]: 2025-09-25 08:37:24 Age [y:d:h:m:s]: 00:100:20:15:46
Block: 1376028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72216 RingCT/type: yes/0
Extra: 0115f3905cda23ea81b35df55e321c072fca87f7bc0b2c0fec88f3827814ec9a0f021100000006b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cec94fc9083a502c3f6cd6674c24944033a446c43db7548f6e37ee5951485f2 0.600000000000 1864119 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": 1376038, "vin": [ { "gen": { "height": 1376028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cec94fc9083a502c3f6cd6674c24944033a446c43db7548f6e37ee5951485f2" } } ], "extra": [ 1, 21, 243, 144, 92, 218, 35, 234, 129, 179, 93, 245, 94, 50, 28, 7, 47, 202, 135, 247, 188, 11, 44, 15, 236, 136, 243, 130, 120, 20, 236, 154, 15, 2, 17, 0, 0, 0, 6, 178, 247, 132, 196, 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