Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a46e3ea2a825652a50567c2d39c00f8e4e9a3d8e98854564eca95338762fc7bd

Tx prefix hash: 2a1105e741948346439cd337e21d7e4e00cd67ca0d7504ebcfd4a7bbd5620421
Tx public key: 38bafdf85b281ecb14fad45dbd22f6b28fa62e4f942cfecb193e962cdb04855a
Timestamp: 1721232985 Timestamp [UCT]: 2024-07-17 16:16:25 Age [y:d:h:m:s]: 00:257:21:02:44
Block: 1067792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184198 RingCT/type: yes/0
Extra: 0138bafdf85b281ecb14fad45dbd22f6b28fa62e4f942cfecb193e962cdb04855a02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f0d0239a95ee7adc8e8e3a048eed1297150100da8e3ded81c6c88003608f654 0.600000000000 1538703 of 15

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": 1067802, "vin": [ { "gen": { "height": 1067792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f0d0239a95ee7adc8e8e3a048eed1297150100da8e3ded81c6c88003608f654" } } ], "extra": [ 1, 56, 186, 253, 248, 91, 40, 30, 203, 20, 250, 212, 93, 189, 34, 246, 178, 143, 166, 46, 79, 148, 44, 254, 203, 25, 62, 150, 44, 219, 4, 133, 90, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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