Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 763e0ad95e4e53c2b3cb2f9e0da011fbb12ecbc2dbeb8606d021dc52bbc34722

Tx prefix hash: aa82a81d9457ce18a59d841cd7f2ecd0c4cdeb16f69c9bfb6e297eb5bb7098d3
Tx public key: 44d81c13e2d02188e3f4711518882def9459ee412772062d3e33f42bffcc07d4
Timestamp: 1706112765 Timestamp [UCT]: 2024-01-24 16:12:45 Age [y:d:h:m:s]: 01:339:01:25:19
Block: 942397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501209 RingCT/type: yes/0
Extra: 0144d81c13e2d02188e3f4711518882def9459ee412772062d3e33f42bffcc07d40211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34ed78c5fc37ba3b648630e5ed85761268d1e7417e0d0145aec8b1198a5552f5 0.600000000000 1400569 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": 942407, "vin": [ { "gen": { "height": 942397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34ed78c5fc37ba3b648630e5ed85761268d1e7417e0d0145aec8b1198a5552f5" } } ], "extra": [ 1, 68, 216, 28, 19, 226, 208, 33, 136, 227, 244, 113, 21, 24, 136, 45, 239, 148, 89, 238, 65, 39, 114, 6, 45, 62, 51, 244, 43, 255, 204, 7, 212, 2, 17, 0, 0, 0, 6, 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