Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c73961aaec4cb37d15844ce991741fdaebe1f4f614c73962c0d747bfb86dd98

Tx prefix hash: 2b361d7c75caa317c16e0c10f0f6f192ed1204048eecae0efdc1952a8faea034
Tx public key: 1e8174e2494761dcf77279107130b3fc322877294282ef5e19f4fbf6a904d47c
Timestamp: 1699774372 Timestamp [UCT]: 2023-11-12 07:32:52 Age [y:d:h:m:s]: 01:126:04:37:25
Block: 889880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351384 RingCT/type: yes/0
Extra: 011e8174e2494761dcf77279107130b3fc322877294282ef5e19f4fbf6a904d47c02110000000274c3735f000000000000000000

1 output(s) for total of 0.690968345000 dcy

stealth address amount amount idx
00: 8520045e106bb5e565c82f9d4a0bf41bc4c6b9f2989de9e7d88ac0f9035b866f 0.690968345000 1345897 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": 889890, "vin": [ { "gen": { "height": 889880 } } ], "vout": [ { "amount": 690968345, "target": { "key": "8520045e106bb5e565c82f9d4a0bf41bc4c6b9f2989de9e7d88ac0f9035b866f" } } ], "extra": [ 1, 30, 129, 116, 226, 73, 71, 97, 220, 247, 114, 121, 16, 113, 48, 179, 252, 50, 40, 119, 41, 66, 130, 239, 94, 25, 244, 251, 246, 169, 4, 212, 124, 2, 17, 0, 0, 0, 2, 116, 195, 115, 95, 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