Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74f1fa5e394b94700f1dbeeb079e88f6211146f4b518cd6c6c155a5cfa3a7344

Tx prefix hash: a40aa8ae190309f61a433e7c9a64ac11deab5143e145790e3f0e526a9e9a8a21
Tx public key: 3bd35ff75de1de472ad1de526fda38bf9e99ff8e9ba23319c1034b2fd34283b8
Timestamp: 1702839019 Timestamp [UCT]: 2023-12-17 18:50:19 Age [y:d:h:m:s]: 01:110:07:46:43
Block: 915283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339973 RingCT/type: yes/0
Extra: 013bd35ff75de1de472ad1de526fda38bf9e99ff8e9ba23319c1034b2fd34283b8021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3607639eab5272a139d3264aba5933bfda1f6d4b9c9db12db990acf49f9e984f 0.600000000000 1372675 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": 915293, "vin": [ { "gen": { "height": 915283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3607639eab5272a139d3264aba5933bfda1f6d4b9c9db12db990acf49f9e984f" } } ], "extra": [ 1, 59, 211, 95, 247, 93, 225, 222, 71, 42, 209, 222, 82, 111, 218, 56, 191, 158, 153, 255, 142, 155, 162, 51, 25, 193, 3, 75, 47, 211, 66, 131, 184, 2, 17, 0, 0, 0, 8, 230, 210, 127, 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