Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ed6053d77340793869d3e84e9d158e3440c7d021d4856ad1bb9e34523699ba0

Tx prefix hash: a1ec3696f71858bb8d28ee2d921a793debc82567ea5ed4f11e5d573522973c7f
Tx public key: bc065374745f1cf995f3c64ef2603d7c3c472da3d0390b2e1aa98ac5c4388350
Timestamp: 1582291946 Timestamp [UCT]: 2020-02-21 13:32:26 Age [y:d:h:m:s]: 04:271:10:28:58
Block: 69493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1086532 RingCT/type: yes/0
Extra: 01bc065374745f1cf995f3c64ef2603d7c3c472da3d0390b2e1aa98ac5c438835002110000000103d36d11000000000000000000

1 output(s) for total of 361.194931581000 dcy

stealth address amount amount idx
00: d24a3540fa98a82d859b1bfd9d4cd243f08641a330282de913039d66e0fe9b43 361.194931581000 128192 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": 69503, "vin": [ { "gen": { "height": 69493 } } ], "vout": [ { "amount": 361194931581, "target": { "key": "d24a3540fa98a82d859b1bfd9d4cd243f08641a330282de913039d66e0fe9b43" } } ], "extra": [ 1, 188, 6, 83, 116, 116, 95, 28, 249, 149, 243, 198, 78, 242, 96, 61, 124, 60, 71, 45, 163, 208, 57, 11, 46, 26, 169, 138, 197, 196, 56, 131, 80, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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