Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b22aa3e6fc1539b9e8e995ba7bb96430c627195be54545ada5d27272b101219

Tx prefix hash: 0b7d462e31b326f38bfab45bf18b62711ebd39b3304efd163cb35118f069c0af
Tx public key: e6a094a2995bc5bd84e99ac19afcb13b2c4bf3524b7cde78bcf88754f5c22730
Timestamp: 1697322792 Timestamp [UCT]: 2023-10-14 22:33:12 Age [y:d:h:m:s]: 01:133:06:04:29
Block: 869755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356224 RingCT/type: yes/0
Extra: 01e6a094a2995bc5bd84e99ac19afcb13b2c4bf3524b7cde78bcf88754f5c227300211000000024b8f5122000000000000000000

1 output(s) for total of 0.805639331000 dcy

stealth address amount amount idx
00: 07df213656d5be3a250c92150300981acc11145321e488276ff4c8d2e64fc52d 0.805639331000 1324610 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": 869765, "vin": [ { "gen": { "height": 869755 } } ], "vout": [ { "amount": 805639331, "target": { "key": "07df213656d5be3a250c92150300981acc11145321e488276ff4c8d2e64fc52d" } } ], "extra": [ 1, 230, 160, 148, 162, 153, 91, 197, 189, 132, 233, 154, 193, 154, 252, 177, 59, 44, 75, 243, 82, 75, 124, 222, 120, 188, 248, 135, 84, 245, 194, 39, 48, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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