Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 894ad59f9eec8a137d7dc4a2a595ec9357e3748c07aba4f9acada5c41654c6fa

Tx prefix hash: c3e8d85273e60c92880740c3e2a6b500e49047c39261f9f02e139f1b6f383ce8
Tx public key: 6a38fbdeb667fd5da45fc72fae576a796538b8d0cfb385f2cdc486996e48185b
Timestamp: 1758615312 Timestamp [UCT]: 2025-09-23 08:15:12 Age [y:d:h:m:s]: 00:106:22:37:56
Block: 1374581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76584 RingCT/type: yes/0
Extra: 016a38fbdeb667fd5da45fc72fae576a796538b8d0cfb385f2cdc486996e48185b021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44368ea54080e12a632c2eee5449296d2d1720a3d1e3bc8059e52c6baed075e8 0.600000000000 1862666 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": 1374591, "vin": [ { "gen": { "height": 1374581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44368ea54080e12a632c2eee5449296d2d1720a3d1e3bc8059e52c6baed075e8" } } ], "extra": [ 1, 106, 56, 251, 222, 182, 103, 253, 93, 164, 95, 199, 47, 174, 87, 106, 121, 101, 56, 184, 208, 207, 179, 133, 242, 205, 196, 134, 153, 110, 72, 24, 91, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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