Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e23b466fdcae0fd8a100a137c711001d471b99fa105d5269554c4252bb43ecdc

Tx prefix hash: 0e7d92c45985d5b49341d624b99827d77e3973c16b0b12a047f96c4dbd056c11
Tx public key: 8d1c088cb9591c38c4d56e281a47d2654deb281eced7fd9efebfdd579bb36ffb
Timestamp: 1659465982 Timestamp [UCT]: 2022-08-02 18:46:22 Age [y:d:h:m:s]: 02:195:20:32:38
Block: 557285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 661170 RingCT/type: yes/0
Extra: 018d1c088cb9591c38c4d56e281a47d2654deb281eced7fd9efebfdd579bb36ffb021100000001eae24e24000000000000000000

1 output(s) for total of 8.739439426000 dcy

stealth address amount amount idx
00: 56e691eabfdde1b621820cd105215382a1022ef3114aa4858ba7fdded2040221 8.739439426000 989289 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": 557295, "vin": [ { "gen": { "height": 557285 } } ], "vout": [ { "amount": 8739439426, "target": { "key": "56e691eabfdde1b621820cd105215382a1022ef3114aa4858ba7fdded2040221" } } ], "extra": [ 1, 141, 28, 8, 140, 185, 89, 28, 56, 196, 213, 110, 40, 26, 71, 210, 101, 77, 235, 40, 30, 206, 215, 253, 158, 254, 191, 221, 87, 155, 179, 111, 251, 2, 17, 0, 0, 0, 1, 234, 226, 78, 36, 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