Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d211ebc9f4aa80e731494794ad33f1e4ef44e9b2e9444efc6a61c556744d42e

Tx prefix hash: 2d8ad79929b0c2fb797e54799c9dda107e1274828b42e693ae8a6bf3a44cf473
Tx public key: 20e1ecbcc3434ad7ceb08a4086741251acbf066153229cb7a642b83a5804a213
Timestamp: 1672613180 Timestamp [UCT]: 2023-01-01 22:46:20 Age [y:d:h:m:s]: 02:095:05:30:24
Block: 665560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 589748 RingCT/type: yes/0
Extra: 0120e1ecbcc3434ad7ceb08a4086741251acbf066153229cb7a642b83a5804a2130211000000025029cbac000000000000000000

1 output(s) for total of 3.825809988000 dcy

stealth address amount amount idx
00: 0d0f0cf2b5684722aa43aa41fe428dc13f6dfcb27e9714c7307529feacf32b53 3.825809988000 1106609 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": 665570, "vin": [ { "gen": { "height": 665560 } } ], "vout": [ { "amount": 3825809988, "target": { "key": "0d0f0cf2b5684722aa43aa41fe428dc13f6dfcb27e9714c7307529feacf32b53" } } ], "extra": [ 1, 32, 225, 236, 188, 195, 67, 74, 215, 206, 176, 138, 64, 134, 116, 18, 81, 172, 191, 6, 97, 83, 34, 156, 183, 166, 66, 184, 58, 88, 4, 162, 19, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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