Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22c3035b13330a337848f301323af81e8347d373d0047e4d0c936c2fd645058d

Tx prefix hash: ee5fb21ac4bc2faf03d2efa7c58429aa31fe35e7251ab22e6db7bd78988fec52
Tx public key: 1707498e0f3d1f3ef2111a8ba2ba72d89e8c8575c35b2358b8c5c1991946b7ca
Timestamp: 1581947870 Timestamp [UCT]: 2020-02-17 13:57:50 Age [y:d:h:m:s]: 04:315:18:17:32
Block: 66764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118126 RingCT/type: yes/0
Extra: 011707498e0f3d1f3ef2111a8ba2ba72d89e8c8575c35b2358b8c5c1991946b7ca021100000002c71d3ff9000000000000000000

1 output(s) for total of 368.794097291000 dcy

stealth address amount amount idx
00: f287ebd6a7fa3aff9a7b34628446b1eced4aae9a60d70c06aa3218c0633cb61d 368.794097291000 122948 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": 66774, "vin": [ { "gen": { "height": 66764 } } ], "vout": [ { "amount": 368794097291, "target": { "key": "f287ebd6a7fa3aff9a7b34628446b1eced4aae9a60d70c06aa3218c0633cb61d" } } ], "extra": [ 1, 23, 7, 73, 142, 15, 61, 31, 62, 242, 17, 26, 139, 162, 186, 114, 216, 158, 140, 133, 117, 195, 91, 35, 88, 184, 197, 193, 153, 25, 70, 183, 202, 2, 17, 0, 0, 0, 2, 199, 29, 63, 249, 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