Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a813a7e7249dd1b995dc67bf76aef5526199fe971f85097c8ba639562a5690df

Tx prefix hash: 7dc9366e1578e8fd1a5d2f141b09aa8aa80c1f622b0950584bded18a70479021
Tx public key: 1da57dbc2139a5b04ea40528e33c6b4e2682eaf6f47663d69b8f02cbe32b3dca
Timestamp: 1708716414 Timestamp [UCT]: 2024-02-23 19:26:54 Age [y:d:h:m:s]: 01:073:03:30:08
Block: 964007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313320 RingCT/type: yes/0
Extra: 011da57dbc2139a5b04ea40528e33c6b4e2682eaf6f47663d69b8f02cbe32b3dca021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c75fd577e5c8c25f33acda1f20478e19980a83c01d0a05b7ab55e8cb25eba2b7 0.600000000000 1423734 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": 964017, "vin": [ { "gen": { "height": 964007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c75fd577e5c8c25f33acda1f20478e19980a83c01d0a05b7ab55e8cb25eba2b7" } } ], "extra": [ 1, 29, 165, 125, 188, 33, 57, 165, 176, 78, 164, 5, 40, 227, 60, 107, 78, 38, 130, 234, 246, 244, 118, 99, 214, 155, 143, 2, 203, 227, 43, 61, 202, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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