Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e17c02a4ec78410b4ee584486d8982cc82290eae78b32cfd60706183cb968a9

Tx prefix hash: ddc052ddee24488501243312712004dfaf92555e91d75ad10153b966c4e510ce
Tx public key: 83eba462d6bf10c47d3f12fcbae178b7e16d6f1585173e212fbd6e026876c92b
Timestamp: 1735405177 Timestamp [UCT]: 2024-12-28 16:59:37 Age [y:d:h:m:s]: 01:004:01:09:15
Block: 1185141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261344 RingCT/type: yes/0
Extra: 0183eba462d6bf10c47d3f12fcbae178b7e16d6f1585173e212fbd6e026876c92b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4de68d62938ff58c8c0aa9aa89d36e6ca71b5969ce519d7b61f9ec9a9441d25 0.600000000000 1671606 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": 1185151, "vin": [ { "gen": { "height": 1185141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4de68d62938ff58c8c0aa9aa89d36e6ca71b5969ce519d7b61f9ec9a9441d25" } } ], "extra": [ 1, 131, 235, 164, 98, 214, 191, 16, 196, 125, 63, 18, 252, 186, 225, 120, 183, 225, 109, 111, 21, 133, 23, 62, 33, 47, 189, 110, 2, 104, 118, 201, 43, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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