Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4486fe0dae219971248de596c2fc124eb03cd1e4ecc4dc8b8aed71c5abc4c10e

Tx prefix hash: ad0f61643a2a585149a96447f74f24a108f263d454a12994dfe2b32095aace8a
Tx public key: 79f000063e5f8bf0c82e7e20bd3ccbaf4c271eccaa37c69e3b07189760cf419a
Timestamp: 1749521622 Timestamp [UCT]: 2025-06-10 02:13:42 Age [y:d:h:m:s]: 00:163:17:08:48
Block: 1301761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114680 RingCT/type: yes/0
Extra: 0179f000063e5f8bf0c82e7e20bd3ccbaf4c271eccaa37c69e3b07189760cf419a021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91db4e453a5bc8f4ab18f8a4a8cee4319760da9bd221718946e4d5854f6f787b 0.600000000000 1789322 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": 1301771, "vin": [ { "gen": { "height": 1301761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91db4e453a5bc8f4ab18f8a4a8cee4319760da9bd221718946e4d5854f6f787b" } } ], "extra": [ 1, 121, 240, 0, 6, 62, 95, 139, 240, 200, 46, 126, 32, 189, 60, 203, 175, 76, 39, 30, 204, 170, 55, 198, 158, 59, 7, 24, 151, 96, 207, 65, 154, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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