Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbb5974df8a05618ae6fffc6e9b05164a29e33c9752979095e94d653d2a7e5fd

Tx prefix hash: e63baa697977e6b6623e37e124e253cb47fa43fd48e154f1ce2b51949017a501
Tx public key: 8d5168b2995ee40b3e122d88226eac635163527ae11bd781a8da2d152f4c61be
Timestamp: 1763536906 Timestamp [UCT]: 2025-11-19 07:21:46 Age [y:d:h:m:s]: 00:034:01:26:33
Block: 1415372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24386 RingCT/type: yes/0
Extra: 018d5168b2995ee40b3e122d88226eac635163527ae11bd781a8da2d152f4c61be02110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4046d584b6094589b94451df5a44f17ddd4c0f8b7b825abbab307adc1585b8f0 0.600000000000 1903873 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": 1415382, "vin": [ { "gen": { "height": 1415372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4046d584b6094589b94451df5a44f17ddd4c0f8b7b825abbab307adc1585b8f0" } } ], "extra": [ 1, 141, 81, 104, 178, 153, 94, 228, 11, 62, 18, 45, 136, 34, 110, 172, 99, 81, 99, 82, 122, 225, 27, 215, 129, 168, 218, 45, 21, 47, 76, 97, 190, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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