Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c139f1e65893788e2fa7466e061f504eda1506f14cd6e8f18d3374463731406

Tx prefix hash: 7e0d1f00bfeb4af026e8b56cb49bdbdf9ea54b6b77b0deede6ef3d6b87c5171e
Tx public key: 5261c91a2fd5abe5cbb59a72f5d03c7526fb19966d734cc733b807f355295441
Timestamp: 1701554888 Timestamp [UCT]: 2023-12-02 22:08:08 Age [y:d:h:m:s]: 01:181:13:40:40
Block: 904632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390973 RingCT/type: yes/0
Extra: 015261c91a2fd5abe5cbb59a72f5d03c7526fb19966d734cc733b807f35529544102110000000633af99f4000000000000000000

1 output(s) for total of 0.617417066000 dcy

stealth address amount amount idx
00: 381b19a463adbb0cc83fe1f1ce5ef9642abebecf230249f149e5a1ccaad4c7b3 0.617417066000 1361401 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": 904642, "vin": [ { "gen": { "height": 904632 } } ], "vout": [ { "amount": 617417066, "target": { "key": "381b19a463adbb0cc83fe1f1ce5ef9642abebecf230249f149e5a1ccaad4c7b3" } } ], "extra": [ 1, 82, 97, 201, 26, 47, 213, 171, 229, 203, 181, 154, 114, 245, 208, 60, 117, 38, 251, 25, 150, 109, 115, 76, 199, 51, 184, 7, 243, 85, 41, 84, 65, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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