Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 289a6ec2ded0e4ea5558c42643df8b2c5ef6ea23abbac28dd84e0ce53618fc03

Tx prefix hash: ea78a60808dae69efc221bb43cf944ccd42789d5100cc38aa66962a79a109689
Tx public key: d62d341b8c1ae90f49fb3fa59f3a223e1cf3c3843c6d45aa05c6f48dddfcbc7b
Timestamp: 1650930113 Timestamp [UCT]: 2022-04-25 23:41:53 Age [y:d:h:m:s]: 02:216:04:49:59
Block: 488154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 674440 RingCT/type: yes/0
Extra: 01d62d341b8c1ae90f49fb3fa59f3a223e1cf3c3843c6d45aa05c6f48dddfcbc7b02110000000375e3f0e9000000000000000000

1 output(s) for total of 14.809601702000 dcy

stealth address amount amount idx
00: 939f566e0ec5f4f01b31bf6e3e7162e2107cb74f1131ea550dfb826bd9b8aa19 14.809601702000 910759 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": 488164, "vin": [ { "gen": { "height": 488154 } } ], "vout": [ { "amount": 14809601702, "target": { "key": "939f566e0ec5f4f01b31bf6e3e7162e2107cb74f1131ea550dfb826bd9b8aa19" } } ], "extra": [ 1, 214, 45, 52, 27, 140, 26, 233, 15, 73, 251, 63, 165, 159, 58, 34, 62, 28, 243, 195, 132, 60, 109, 69, 170, 5, 198, 244, 141, 221, 252, 188, 123, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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