Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c086559c026cc66afdd665bc12728d5194e8a4a75b70e965f3e1c52d92ca167

Tx prefix hash: ef3a3e53f0b775754958fbe385812afbce11a198916b48537144fac1386cdd04
Tx public key: 79e2c8a46cde53a5b81908f11ed8014a4c05d4f9667b4e433c665f345cc6f4ba
Timestamp: 1750576921 Timestamp [UCT]: 2025-06-22 07:22:01 Age [y:d:h:m:s]: 00:149:07:17:44
Block: 1310301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104570 RingCT/type: yes/0
Extra: 0179e2c8a46cde53a5b81908f11ed8014a4c05d4f9667b4e433c665f345cc6f4ba02110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbb5b0110f9912fcf055c7a5dc6f8faf0860667ae0c8d44df71d40cd169e424b 0.600000000000 1797920 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": 1310311, "vin": [ { "gen": { "height": 1310301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbb5b0110f9912fcf055c7a5dc6f8faf0860667ae0c8d44df71d40cd169e424b" } } ], "extra": [ 1, 121, 226, 200, 164, 108, 222, 83, 165, 184, 25, 8, 241, 30, 216, 1, 74, 76, 5, 212, 249, 102, 123, 78, 67, 60, 102, 95, 52, 92, 198, 244, 186, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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