Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caf89802f7c4b53737ddf88e287b233c6faa6dee8c329d48b64e06567734e114

Tx prefix hash: b9ae776a49a4c88f5b471abb0a3a3f349e7852dd610e067960e6e6686f86f6bc
Tx public key: 0ac5f2bf8abbb7840df90b0e99a033828752c3d4371fb1121c98fcf15bf3e5e9
Timestamp: 1700520910 Timestamp [UCT]: 2023-11-20 22:55:10 Age [y:d:h:m:s]: 01:207:12:29:01
Block: 896057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409444 RingCT/type: yes/0
Extra: 010ac5f2bf8abbb7840df90b0e99a033828752c3d4371fb1121c98fcf15bf3e5e9021100000004faf35c9c000000000000000000

1 output(s) for total of 0.659160504000 dcy

stealth address amount amount idx
00: c911fc769cae6af66ae81ac6a54ecdf100c8d67c21746099c031aae493e47ec1 0.659160504000 1352308 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": 896067, "vin": [ { "gen": { "height": 896057 } } ], "vout": [ { "amount": 659160504, "target": { "key": "c911fc769cae6af66ae81ac6a54ecdf100c8d67c21746099c031aae493e47ec1" } } ], "extra": [ 1, 10, 197, 242, 191, 138, 187, 183, 132, 13, 249, 11, 14, 153, 160, 51, 130, 135, 82, 195, 212, 55, 31, 177, 18, 28, 152, 252, 241, 91, 243, 229, 233, 2, 17, 0, 0, 0, 4, 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