Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0d8a6a61ddf0e4651644a0806bad15beb1e314deb02011816ba6425e81d902

Tx prefix hash: e90590384b608c7da503ba9a114bbe50e37a0bd69fdd85aefaa5fd94d3e8b6ca
Tx public key: 7368a7e3a8339e96b37fe375397aba4f4bf06b24c274d0eeedaf782dd63cf1c5
Timestamp: 1724681719 Timestamp [UCT]: 2024-08-26 14:15:19 Age [y:d:h:m:s]: 00:235:00:32:11
Block: 1096364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167849 RingCT/type: yes/0
Extra: 017368a7e3a8339e96b37fe375397aba4f4bf06b24c274d0eeedaf782dd63cf1c5021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54062038806c3b92a3b9a1d608f0f4b2e9f7e0b44b5606547350151d3be7e9dc 0.600000000000 1571553 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": 1096374, "vin": [ { "gen": { "height": 1096364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54062038806c3b92a3b9a1d608f0f4b2e9f7e0b44b5606547350151d3be7e9dc" } } ], "extra": [ 1, 115, 104, 167, 227, 168, 51, 158, 150, 179, 127, 227, 117, 57, 122, 186, 79, 75, 240, 107, 36, 194, 116, 208, 238, 237, 175, 120, 45, 214, 60, 241, 197, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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