Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72002be0d040ed95ca1630b3d02fcaabe14b76250280a886dfdc253fb25f0e34

Tx prefix hash: b481c430e4fa28498d7c44778bc340ee1ddd2fe50b8ea9351d740a81a0bb70b0
Tx public key: c9c243fa1509c4aa0cf5c4ccb5d55ce9d276b0b1d8045ce73518a3f27862607c
Timestamp: 1756968583 Timestamp [UCT]: 2025-09-04 06:49:43 Age [y:d:h:m:s]: 00:143:22:22:59
Block: 1361008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102805 RingCT/type: yes/0
Extra: 01c9c243fa1509c4aa0cf5c4ccb5d55ce9d276b0b1d8045ce73518a3f27862607c021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbfecabb9e352606214cdd583d08346ca8915b2df86cedc84aebb6f309d27057 0.600000000000 1849021 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": 1361018, "vin": [ { "gen": { "height": 1361008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbfecabb9e352606214cdd583d08346ca8915b2df86cedc84aebb6f309d27057" } } ], "extra": [ 1, 201, 194, 67, 250, 21, 9, 196, 170, 12, 245, 196, 204, 181, 213, 92, 233, 210, 118, 176, 177, 216, 4, 92, 231, 53, 24, 163, 242, 120, 98, 96, 124, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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