Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40a5f9f46d08ea9b3838882db732c4e34162af4980a0551353195d379a8cd253

Tx prefix hash: 8cd54d7b756e816e031c5270451af248d2628c143ebd2a993b8c23dfc2cd025f
Tx public key: cb866ce06d90295a79285b668c441c4a7deac6a0d55e2a8946dd0daccb0fdcc2
Timestamp: 1751577504 Timestamp [UCT]: 2025-07-03 21:18:24 Age [y:d:h:m:s]: 00:129:06:53:49
Block: 1318180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90656 RingCT/type: yes/0
Extra: 01cb866ce06d90295a79285b668c441c4a7deac6a0d55e2a8946dd0daccb0fdcc2021100000009bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17a652e281c88c61b316ed3b2bf1c0e58864c2244bb15c62295da600e87effd6 0.600000000000 1805855 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": 1318190, "vin": [ { "gen": { "height": 1318180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17a652e281c88c61b316ed3b2bf1c0e58864c2244bb15c62295da600e87effd6" } } ], "extra": [ 1, 203, 134, 108, 224, 109, 144, 41, 90, 121, 40, 91, 102, 140, 68, 28, 74, 125, 234, 198, 160, 213, 94, 42, 137, 70, 221, 13, 172, 203, 15, 220, 194, 2, 17, 0, 0, 0, 9, 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