Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8473db7b0ce3d3d525cb45953c81806d3f31ea1de40a8830971b3a0add37d1c

Tx prefix hash: 1a566e6c3c048331b2bf608e088bda028dee1f54caf0a75a3f2d970cefcc347f
Tx public key: 29b57cdd3eac17d0eb2d1ce6643cf8e57c3ce6edaeb97b0e78f81f2d1b2ad4af
Timestamp: 1699307359 Timestamp [UCT]: 2023-11-06 21:49:19 Age [y:d:h:m:s]: 01:188:20:17:55
Block: 886006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396189 RingCT/type: yes/0
Extra: 0129b57cdd3eac17d0eb2d1ce6643cf8e57c3ce6edaeb97b0e78f81f2d1b2ad4af02110000000533af99f4000000000000000000

1 output(s) for total of 0.711695676000 dcy

stealth address amount amount idx
00: 72bd5637fc7ea6345d6624a43494a4873a950b67b4d5064a620347df3740bb11 0.711695676000 1341809 of 0

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": 886016, "vin": [ { "gen": { "height": 886006 } } ], "vout": [ { "amount": 711695676, "target": { "key": "72bd5637fc7ea6345d6624a43494a4873a950b67b4d5064a620347df3740bb11" } } ], "extra": [ 1, 41, 181, 124, 221, 62, 172, 23, 208, 235, 45, 28, 230, 100, 60, 248, 229, 124, 60, 230, 237, 174, 185, 123, 14, 120, 248, 31, 45, 27, 42, 212, 175, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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