Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d779e1ba1b9b809fbc20ce9d5f457a7fee8e9091236f950ae5f11e7b4200c354

Tx prefix hash: 54c887103503bdc2e53b247330c021fd74702c1823f552564e7a1f12046145e4
Tx public key: 97a3a4247dfd76577097d1b83fcfe9ed3c65a133d5a2a30971225550176737df
Timestamp: 1721165560 Timestamp [UCT]: 2024-07-16 21:32:40 Age [y:d:h:m:s]: 00:268:14:36:25
Block: 1067227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191904 RingCT/type: yes/0
Extra: 0197a3a4247dfd76577097d1b83fcfe9ed3c65a133d5a2a30971225550176737df021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc8a05586bbf1f1b5f02928f5a3edb457faf606ef31af3bba44b4b58dc794e12 0.600000000000 1537986 of 15

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": 1067237, "vin": [ { "gen": { "height": 1067227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc8a05586bbf1f1b5f02928f5a3edb457faf606ef31af3bba44b4b58dc794e12" } } ], "extra": [ 1, 151, 163, 164, 36, 125, 253, 118, 87, 112, 151, 209, 184, 63, 207, 233, 237, 60, 101, 161, 51, 213, 162, 163, 9, 113, 34, 85, 80, 23, 103, 55, 223, 2, 17, 0, 0, 0, 3, 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