Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f0cf5c2b6abdc4cbcf871656b39ce7b3114b901c120768cb05bd4f1cbc29b86

Tx prefix hash: 030d3498c27ce68cc56413710bd10b1fa77f4947850745b331e6c0fb8e471fa3
Tx public key: b9d076a91d3c416067dc30d1e41daf169b6aac804a53791d0ef43957bf4806fd
Timestamp: 1720824574 Timestamp [UCT]: 2024-07-12 22:49:34 Age [y:d:h:m:s]: 00:245:16:08:00
Block: 1064403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175514 RingCT/type: yes/0
Extra: 01b9d076a91d3c416067dc30d1e41daf169b6aac804a53791d0ef43957bf4806fd02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d50854c053b011801b321473b57b26c3ab627f526b334c4daa56c46a7453381 0.600000000000 1534928 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": 1064413, "vin": [ { "gen": { "height": 1064403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d50854c053b011801b321473b57b26c3ab627f526b334c4daa56c46a7453381" } } ], "extra": [ 1, 185, 208, 118, 169, 29, 60, 65, 96, 103, 220, 48, 209, 228, 29, 175, 22, 155, 106, 172, 128, 74, 83, 121, 29, 14, 244, 57, 87, 191, 72, 6, 253, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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