Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b92721d42b29a8fbacbca23ff2473895b1d13d8b27c090f29402bf45eed3452d

Tx prefix hash: 0887145cf7e0acb76ff79c4cf235b0cfa1a16d84f832ac460b0e3f4061a5e133
Tx public key: 989d0e4eadce123307b1b42ae13c932ee5f842215bf13f266dc1fa40e946ad9d
Timestamp: 1762757542 Timestamp [UCT]: 2025-11-10 06:52:22 Age [y:d:h:m:s]: 00:018:01:55:46
Block: 1408910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12944 RingCT/type: yes/0
Extra: 01989d0e4eadce123307b1b42ae13c932ee5f842215bf13f266dc1fa40e946ad9d021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97a10c3889d3980471004ac57a09fa991ca81ca53d96df4ab9fdf759470052b6 0.600000000000 1897341 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": 1408920, "vin": [ { "gen": { "height": 1408910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97a10c3889d3980471004ac57a09fa991ca81ca53d96df4ab9fdf759470052b6" } } ], "extra": [ 1, 152, 157, 14, 78, 173, 206, 18, 51, 7, 177, 180, 42, 225, 60, 147, 46, 229, 248, 66, 33, 91, 241, 63, 38, 109, 193, 250, 64, 233, 70, 173, 157, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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