Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73e7581795cecf6cf68c9dfd6906b203db7744dcf0c320d96f0f26c8ab35b665

Tx prefix hash: fabd3fd48cbb8f1af23eadb861da61549dcb458bd6fd0f723ff550d0baccfd5f
Tx public key: cbf24db7df5170e975cdd4728fe8040f4d13dd8ad11d655e5175ecb88c6ce7b1
Timestamp: 1674654320 Timestamp [UCT]: 2023-01-25 13:45:20 Age [y:d:h:m:s]: 02:128:19:02:42
Block: 682495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 613742 RingCT/type: yes/0
Extra: 01cbf24db7df5170e975cdd4728fe8040f4d13dd8ad11d655e5175ecb88c6ce7b10211000000025029cbac000000000000000000

1 output(s) for total of 3.362100465000 dcy

stealth address amount amount idx
00: 06fd70d5ef78b3d55de5161ed53ead26ef8a407c89eaf0d748dc3328123b8393 3.362100465000 1124620 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": 682505, "vin": [ { "gen": { "height": 682495 } } ], "vout": [ { "amount": 3362100465, "target": { "key": "06fd70d5ef78b3d55de5161ed53ead26ef8a407c89eaf0d748dc3328123b8393" } } ], "extra": [ 1, 203, 242, 77, 183, 223, 81, 112, 233, 117, 205, 212, 114, 143, 232, 4, 15, 77, 19, 221, 138, 209, 29, 101, 94, 81, 117, 236, 184, 140, 108, 231, 177, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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