Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d0a38cc04e8d42c9c23d69dcdf44f40141f3e153b3f433c7157bbcdc91f8f91

Tx prefix hash: 49be838571b01ca73821b78d26d3e1907af224f78dd038c3d73d00ab5fd11dee
Tx public key: c0630aa5d42c21c6c5f2061f44c9957fa8166a5cca04626dcbf7c47cad3cbcfc
Timestamp: 1761720833 Timestamp [UCT]: 2025-10-29 06:53:53 Age [y:d:h:m:s]: 00:055:17:21:08
Block: 1400333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39874 RingCT/type: yes/0
Extra: 01c0630aa5d42c21c6c5f2061f44c9957fa8166a5cca04626dcbf7c47cad3cbcfc02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: beb7ac8684bf585a36db49bb81321a6aa64ab64a202857bef628dfdb6ca553b0 0.600000000000 1888640 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": 1400343, "vin": [ { "gen": { "height": 1400333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "beb7ac8684bf585a36db49bb81321a6aa64ab64a202857bef628dfdb6ca553b0" } } ], "extra": [ 1, 192, 99, 10, 165, 212, 44, 33, 198, 197, 242, 6, 31, 68, 201, 149, 127, 168, 22, 106, 92, 202, 4, 98, 109, 203, 247, 196, 124, 173, 60, 188, 252, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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