Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11bc5e7ff662270144269f177b8902ad9bf03a3ba1133156263c437b33fed0d9

Tx prefix hash: 0abf5ccd7d68cbf0a041c69f0761e3dafe51777f2974820dfd8d1175c15db79f
Tx public key: 90ae5477ee9bb97ab02fa4b8a71406881c9e9a5395fe6ae0e9f292ed6551962f
Timestamp: 1737111384 Timestamp [UCT]: 2025-01-17 10:56:24 Age [y:d:h:m:s]: 00:152:13:51:04
Block: 1199272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108736 RingCT/type: yes/0
Extra: 0190ae5477ee9bb97ab02fa4b8a71406881c9e9a5395fe6ae0e9f292ed6551962f021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36650fdeb6730c71e4c5e0435ca732dd1c3f1d3ec378b72b3e8c4e743e8d79d1 0.600000000000 1685901 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": 1199282, "vin": [ { "gen": { "height": 1199272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36650fdeb6730c71e4c5e0435ca732dd1c3f1d3ec378b72b3e8c4e743e8d79d1" } } ], "extra": [ 1, 144, 174, 84, 119, 238, 155, 185, 122, 176, 47, 164, 184, 167, 20, 6, 136, 28, 158, 154, 83, 149, 254, 106, 224, 233, 242, 146, 237, 101, 81, 150, 47, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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