Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7522ab2292f16f8b3520d0b7db6165d94e0d321e5f982ab5a4696e7403e64725

Tx prefix hash: 19f079da86e3d08aaab2988f14ef05cab81dc36d97a8bad0e200e18ac244a1b6
Tx public key: aaef68b080c793ca8e0dd9909ee8ad6e6cb6d2721765a943dac968d557835848
Timestamp: 1755941084 Timestamp [UCT]: 2025-08-23 09:24:44 Age [y:d:h:m:s]: 00:085:16:41:10
Block: 1352601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61177 RingCT/type: yes/0
Extra: 01aaef68b080c793ca8e0dd9909ee8ad6e6cb6d2721765a943dac968d5578358480211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5798aae7d18bb16f6f550014e8a76e199d82cc6d0dbbc0da641750a6a9db067f 0.600000000000 1840566 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": 1352611, "vin": [ { "gen": { "height": 1352601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5798aae7d18bb16f6f550014e8a76e199d82cc6d0dbbc0da641750a6a9db067f" } } ], "extra": [ 1, 170, 239, 104, 176, 128, 199, 147, 202, 142, 13, 217, 144, 158, 232, 173, 110, 108, 182, 210, 114, 23, 101, 169, 67, 218, 201, 104, 213, 87, 131, 88, 72, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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