Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1464af32ed246e62ef5ec6b0292c0b94dbd68be7864ea4ee749f881b30b7505

Tx prefix hash: 8a38fbb82057113d56729ac64e832d0db10660c1f535c4a49c967972e7d9697f
Tx public key: 0e6466e926c5bf062f28d2865a5c05cc65ce35cee9cbd51c71b90d3fb713cac9
Timestamp: 1694244447 Timestamp [UCT]: 2023-09-09 07:27:27 Age [y:d:h:m:s]: 01:270:20:38:08
Block: 844213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454729 RingCT/type: yes/0
Extra: 010e6466e926c5bf062f28d2865a5c05cc65ce35cee9cbd51c71b90d3fb713cac9021100000001faf35c9c000000000000000000

1 output(s) for total of 0.978975778000 dcy

stealth address amount amount idx
00: 7d6a4aa36affa1f44cfad06638379acaaf83dda1dc1c8b89d5f66fd65a6f8816 0.978975778000 1297509 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": 844223, "vin": [ { "gen": { "height": 844213 } } ], "vout": [ { "amount": 978975778, "target": { "key": "7d6a4aa36affa1f44cfad06638379acaaf83dda1dc1c8b89d5f66fd65a6f8816" } } ], "extra": [ 1, 14, 100, 102, 233, 38, 197, 191, 6, 47, 40, 210, 134, 90, 92, 5, 204, 101, 206, 53, 206, 233, 203, 213, 28, 113, 185, 13, 63, 183, 19, 202, 201, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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