Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12c06b752635d323fd96134ad3af021b64f06d634918121aa4c60f95a14c59e9

Tx prefix hash: 1640f68dba32850bd1996229e9da2d942b0a0a2da6c3beb3b6732fbddd80e37a
Tx public key: e64495b946744b70a2ca9af561c215a5799ffc8fa95575b34b8172ba1f7642db
Timestamp: 1577967505 Timestamp [UCT]: 2020-01-02 12:18:25 Age [y:d:h:m:s]: 05:131:23:34:47
Block: 37212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1244074 RingCT/type: yes/0
Extra: 01e64495b946744b70a2ca9af561c215a5799ffc8fa95575b34b8172ba1f7642db0211000000094ac5aa02000000000000000000

1 output(s) for total of 462.063909444000 dcy

stealth address amount amount idx
00: 3bf1478a1a2ecd574a41d051f4760d5cdbedb3f5523f5d1b9fed7eb34cfe1427 462.063909444000 63094 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": 37222, "vin": [ { "gen": { "height": 37212 } } ], "vout": [ { "amount": 462063909444, "target": { "key": "3bf1478a1a2ecd574a41d051f4760d5cdbedb3f5523f5d1b9fed7eb34cfe1427" } } ], "extra": [ 1, 230, 68, 149, 185, 70, 116, 75, 112, 162, 202, 154, 245, 97, 194, 21, 165, 121, 159, 252, 143, 169, 85, 117, 179, 75, 129, 114, 186, 31, 118, 66, 219, 2, 17, 0, 0, 0, 9, 74, 197, 170, 2, 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