Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e03d7ea5454587801a0a86fe1538da5f12798b888618904f66187994b07e7b8b

Tx prefix hash: 20f069820944eef4d8027eb43a2cc312238f5d9a44b612fbbd2312b49b85fc5f
Tx public key: 97e5855acba642cc1a2d4e16e1941e9423948c8f55fdf909456f60af002cff93
Timestamp: 1696935320 Timestamp [UCT]: 2023-10-10 10:55:20 Age [y:d:h:m:s]: 01:183:04:03:19
Block: 866546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391946 RingCT/type: yes/0
Extra: 0197e5855acba642cc1a2d4e16e1941e9423948c8f55fdf909456f60af002cff93021100000003faf35c9c000000000000000000

1 output(s) for total of 0.825607090000 dcy

stealth address amount amount idx
00: aa0d05c038d8d3e6dd237f5fe2c4f653d40a32190037b17f6550114c34dd5379 0.825607090000 1321150 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": 866556, "vin": [ { "gen": { "height": 866546 } } ], "vout": [ { "amount": 825607090, "target": { "key": "aa0d05c038d8d3e6dd237f5fe2c4f653d40a32190037b17f6550114c34dd5379" } } ], "extra": [ 1, 151, 229, 133, 90, 203, 166, 66, 204, 26, 45, 78, 22, 225, 148, 30, 148, 35, 148, 140, 143, 85, 253, 249, 9, 69, 111, 96, 175, 0, 44, 255, 147, 2, 17, 0, 0, 0, 3, 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