Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60c887e4b235c4d6d9e8cd64a1f3cc5742ca313abee722140c8f429b8954fe80

Tx prefix hash: cbbb6dcb87d2e6cbd25f30952e8c88d258d295b415fd87b62696c92e9c7205ba
Tx public key: 5bc40f414fa082e13cecc9373392dc4d8b5c27593440f9ec08359cf45c408e4e
Timestamp: 1750206018 Timestamp [UCT]: 2025-06-18 00:20:18 Age [y:d:h:m:s]: 00:156:16:35:57
Block: 1307296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109783 RingCT/type: yes/0
Extra: 015bc40f414fa082e13cecc9373392dc4d8b5c27593440f9ec08359cf45c408e4e021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b0e4315ae8b0bb277439ff4392c90126f5704338418073861419e2878d55257 0.600000000000 1794907 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": 1307306, "vin": [ { "gen": { "height": 1307296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b0e4315ae8b0bb277439ff4392c90126f5704338418073861419e2878d55257" } } ], "extra": [ 1, 91, 196, 15, 65, 79, 160, 130, 225, 60, 236, 201, 55, 51, 146, 220, 77, 139, 92, 39, 89, 52, 64, 249, 236, 8, 53, 156, 244, 92, 64, 142, 78, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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