Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2f9833fffa0ca26403cd9ffbb1c2aab836e393aae15bc7349cc09eba7270021

Tx prefix hash: 39a95e5077a906d8eed4b61ba53d7e6ff3bbd74373ddfb7b17dbf22dadfd47ce
Tx public key: a36b5fe60f6691ad5affcbc914dfca46df6c1a53438193d526a6c23aa0173f44
Timestamp: 1713319699 Timestamp [UCT]: 2024-04-17 02:08:19 Age [y:d:h:m:s]: 01:035:07:38:59
Block: 1002154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286233 RingCT/type: yes/0
Extra: 01a36b5fe60f6691ad5affcbc914dfca46df6c1a53438193d526a6c23aa0173f4402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4042206b81b4aa4e4a59ce26c803ef3d784ce2657b2ded668d1a8d70f71389f4 0.600000000000 1462670 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": 1002164, "vin": [ { "gen": { "height": 1002154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4042206b81b4aa4e4a59ce26c803ef3d784ce2657b2ded668d1a8d70f71389f4" } } ], "extra": [ 1, 163, 107, 95, 230, 15, 102, 145, 173, 90, 255, 203, 201, 20, 223, 202, 70, 223, 108, 26, 83, 67, 129, 147, 213, 38, 166, 194, 58, 160, 23, 63, 68, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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