Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6affb47759b8c323f31c5829b078d20cf0a29d4b31edabaeed1d86866627b17e

Tx prefix hash: 359731f1d4d905235cd6ca958137855c8230b0f170c14ab8f0f6077cc97b6d8e
Tx public key: 88dc14476ef6ded79c0a575def479f69f5eff92831cd76f5160ea534ba4bcff4
Timestamp: 1726523654 Timestamp [UCT]: 2024-09-16 21:54:14 Age [y:d:h:m:s]: 00:115:21:54:08
Block: 1111648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82880 RingCT/type: yes/0
Extra: 0188dc14476ef6ded79c0a575def479f69f5eff92831cd76f5160ea534ba4bcff402110000000ee914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: ad78276b18ab6eb7efbeabae3b0aa2d19410df6f21cb88f34e4b181fee41b0a9 0.608000000000 1590677 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": 1111658, "vin": [ { "gen": { "height": 1111648 } } ], "vout": [ { "amount": 608000000, "target": { "key": "ad78276b18ab6eb7efbeabae3b0aa2d19410df6f21cb88f34e4b181fee41b0a9" } } ], "extra": [ 1, 136, 220, 20, 71, 110, 246, 222, 215, 156, 10, 87, 93, 239, 71, 159, 105, 245, 239, 249, 40, 49, 205, 118, 245, 22, 14, 165, 52, 186, 75, 207, 244, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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