Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aec0743825dfe8c2e5c447085a624bcd0cc2de3252d6c9e4ea44f9366e4d034a

Tx prefix hash: 9d695cb38d27248c9313e0ab9ef857dcf9fd894b6a34692b3db5c76119bed652
Tx public key: f802e9c1910e33595c31fc05525c88cd65dfdce79c7deb87427a7fa100b25e62
Timestamp: 1756156251 Timestamp [UCT]: 2025-08-25 21:10:51 Age [y:d:h:m:s]: 00:150:17:31:18
Block: 1354380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107614 RingCT/type: yes/0
Extra: 01f802e9c1910e33595c31fc05525c88cd65dfdce79c7deb87427a7fa100b25e62021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d91b3e90073de0de1ac85a985b800d04653830dcd31d4f07c47db53365e0094e 0.600000000000 1842367 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": 1354390, "vin": [ { "gen": { "height": 1354380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d91b3e90073de0de1ac85a985b800d04653830dcd31d4f07c47db53365e0094e" } } ], "extra": [ 1, 248, 2, 233, 193, 145, 14, 51, 89, 92, 49, 252, 5, 82, 92, 136, 205, 101, 223, 220, 231, 156, 125, 235, 135, 66, 122, 127, 161, 0, 178, 94, 98, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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