Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7a3fd8781f6919cd71716a182a650a2fe55974db5fb5720eb355cd1c0cfda1c

Tx prefix hash: 6f852e36f6bd572d273472a78a7067d108df44105d1a3ef7d20f235430feb87a
Tx public key: e12f765e109b578fad4df116acbea41d7fc2b9179250f8e598b6da03051aa4c3
Timestamp: 1707788978 Timestamp [UCT]: 2024-02-13 01:49:38 Age [y:d:h:m:s]: 01:098:03:57:49
Block: 956313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331246 RingCT/type: yes/0
Extra: 01e12f765e109b578fad4df116acbea41d7fc2b9179250f8e598b6da03051aa4c30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5cb14ac8b1b055973753189aae128cb71c869ed70b11cee7237458f740021e6 0.600000000000 1415617 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": 956323, "vin": [ { "gen": { "height": 956313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5cb14ac8b1b055973753189aae128cb71c869ed70b11cee7237458f740021e6" } } ], "extra": [ 1, 225, 47, 118, 94, 16, 155, 87, 143, 173, 77, 241, 22, 172, 190, 164, 29, 127, 194, 185, 23, 146, 80, 248, 229, 152, 182, 218, 3, 5, 26, 164, 195, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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