Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08f8a667cb9b5411cd8e5814d95d20dd61241e78316eda02e9e0cabb0621cb33

Tx prefix hash: dd5fc8e187272dad8ff006dd43258780b2e164d7cdcc4f8a2c96f2a78beecc9f
Tx public key: 91e9aecec3adcf0206721f311bc5c6c592fde72707d8440750c9b3d5fd5a60df
Timestamp: 1751720800 Timestamp [UCT]: 2025-07-05 13:06:40 Age [y:d:h:m:s]: 00:185:12:42:58
Block: 1319272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131017 RingCT/type: yes/0
Extra: 0191e9aecec3adcf0206721f311bc5c6c592fde72707d8440750c9b3d5fd5a60df02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7396bb041d46d0b479249fbdac11a75bff78bbd4f173e2112054f60ab89c320e 0.600000000000 1806963 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": 1319282, "vin": [ { "gen": { "height": 1319272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7396bb041d46d0b479249fbdac11a75bff78bbd4f173e2112054f60ab89c320e" } } ], "extra": [ 1, 145, 233, 174, 206, 195, 173, 207, 2, 6, 114, 31, 49, 27, 197, 198, 197, 146, 253, 231, 39, 7, 216, 68, 7, 80, 201, 179, 213, 253, 90, 96, 223, 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