Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5964b25724e2fea6cdf1797091fec062fd4d678128ec5039ed3fd48cbf7a5d93

Tx prefix hash: dc08cb465d826ce03dd90b21b5c171c79bf23dc92664c0bbf3f87caa48e22454
Tx public key: 33a755b5fd401da2a534473be50f59d5cabc8e7bd7b8bebdd11598e41d61203f
Timestamp: 1762527378 Timestamp [UCT]: 2025-11-07 14:56:18 Age [y:d:h:m:s]: 00:046:05:48:54
Block: 1407007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33101 RingCT/type: yes/0
Extra: 0133a755b5fd401da2a534473be50f59d5cabc8e7bd7b8bebdd11598e41d61203f02110000000adf5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b0deb3cd294cf4aa620a451e222d778aa798a6a7189d0dca4a641194c5b6ce2 0.600000000000 1895396 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": 1407017, "vin": [ { "gen": { "height": 1407007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b0deb3cd294cf4aa620a451e222d778aa798a6a7189d0dca4a641194c5b6ce2" } } ], "extra": [ 1, 51, 167, 85, 181, 253, 64, 29, 162, 165, 52, 71, 59, 229, 15, 89, 213, 202, 188, 142, 123, 215, 184, 190, 189, 209, 21, 152, 228, 29, 97, 32, 63, 2, 17, 0, 0, 0, 10, 223, 90, 36, 122, 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