Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a68d9ce09ce40ea7e33ed127d56712ef026204a5fb6b4b0c55dd25d63c1976f9

Tx prefix hash: 029d9ecfab3390daa0c978bb134cde8be77b275eb83b433aecb09dcfbf141896
Tx public key: 5f4eeede79e8ca6aba127e4003305bb3ca58e26f79475b2b8cdbb77e35c6a304
Timestamp: 1726158568 Timestamp [UCT]: 2024-09-12 16:29:28 Age [y:d:h:m:s]: 00:163:05:59:43
Block: 1108603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116474 RingCT/type: yes/0
Extra: 015f4eeede79e8ca6aba127e4003305bb3ca58e26f79475b2b8cdbb77e35c6a304021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 681f9c3b91fc4bbb6cbe7db8c270253ad3df80f2b2dfb08f20917e47b906cdd6 0.600000000000 1586558 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": 1108613, "vin": [ { "gen": { "height": 1108603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "681f9c3b91fc4bbb6cbe7db8c270253ad3df80f2b2dfb08f20917e47b906cdd6" } } ], "extra": [ 1, 95, 78, 238, 222, 121, 232, 202, 106, 186, 18, 126, 64, 3, 48, 91, 179, 202, 88, 226, 111, 121, 71, 91, 43, 140, 219, 183, 126, 53, 198, 163, 4, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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