Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba35f66abf5280d644a5d1c7d93028180cfa9bd5045401ae792f72950ef51372

Tx prefix hash: 9aa40d4e15b8cff66c2e417e5e1ca964368fee6daab38314ac072dc96fb69e23
Tx public key: f482d17730b3649de50657f67e225a3a939eab6847b9252dd7d3c6ce125465d5
Timestamp: 1716602071 Timestamp [UCT]: 2024-05-25 01:54:31 Age [y:d:h:m:s]: 00:300:15:34:47
Block: 1029391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214874 RingCT/type: yes/0
Extra: 01f482d17730b3649de50657f67e225a3a939eab6847b9252dd7d3c6ce125465d502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b7dc8d2f512358d3a8fe40b3a36ab700eeb9ff4088c8122b8ac6ec7bee76939 0.600000000000 1497470 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": 1029401, "vin": [ { "gen": { "height": 1029391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b7dc8d2f512358d3a8fe40b3a36ab700eeb9ff4088c8122b8ac6ec7bee76939" } } ], "extra": [ 1, 244, 130, 209, 119, 48, 179, 100, 157, 229, 6, 87, 246, 126, 34, 90, 58, 147, 158, 171, 104, 71, 185, 37, 45, 215, 211, 198, 206, 18, 84, 101, 213, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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