Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8943143f5ade2cd82fa05f5425ab8e5af2b5279ed2d3a535a8b0ebc48e46d63c

Tx prefix hash: 0e31a32c9738d16d1fb90e8f931e7c500761389ca5e21ab9a9b05797e91bf210
Tx public key: b082c33b4064255cd5b347109c5874eb1d3c9faa56d26354ffba91e398ad22bd
Timestamp: 1705984627 Timestamp [UCT]: 2024-01-23 04:37:07 Age [y:d:h:m:s]: 01:084:19:14:36
Block: 941326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321716 RingCT/type: yes/0
Extra: 01b082c33b4064255cd5b347109c5874eb1d3c9faa56d26354ffba91e398ad22bd0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5639f8a17f8cce00fecaf9d3aef0b47a43c1f3a28b0633c9007c0fcc3d5690d5 0.600000000000 1399472 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": 941336, "vin": [ { "gen": { "height": 941326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5639f8a17f8cce00fecaf9d3aef0b47a43c1f3a28b0633c9007c0fcc3d5690d5" } } ], "extra": [ 1, 176, 130, 195, 59, 64, 100, 37, 92, 213, 179, 71, 16, 156, 88, 116, 235, 29, 60, 159, 170, 86, 210, 99, 84, 255, 186, 145, 227, 152, 173, 34, 189, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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