Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aed68d94e2fc1405c6cdcfda60755d55f37dbad4a9a8ecebdda28240ff5c4cec

Tx prefix hash: aa4a1882b4b857c9145321ed15bae881192196363356af4b7cf27df1415f470c
Tx public key: 7bf8c0fda25356e893d5a26f52ae5cd8464a9094cc97d11b0e10a96de9b4ceac
Timestamp: 1763506700 Timestamp [UCT]: 2025-11-18 22:58:20 Age [y:d:h:m:s]: 00:009:10:08:19
Block: 1415118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6751 RingCT/type: yes/0
Extra: 017bf8c0fda25356e893d5a26f52ae5cd8464a9094cc97d11b0e10a96de9b4ceac021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 310ab40df4a5a9f7bf25d69137a24b7a5d508739ce0e7b090d2d7853415ec93e 0.600000000000 1903613 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": 1415128, "vin": [ { "gen": { "height": 1415118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "310ab40df4a5a9f7bf25d69137a24b7a5d508739ce0e7b090d2d7853415ec93e" } } ], "extra": [ 1, 123, 248, 192, 253, 162, 83, 86, 232, 147, 213, 162, 111, 82, 174, 92, 216, 70, 74, 144, 148, 204, 151, 209, 27, 14, 16, 169, 109, 233, 180, 206, 172, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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