Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 383104f4cee4ac9df0c6ca0a83b6a36141a3530f0da984fe8821c9a1d57f0900

Tx prefix hash: 94d2bebfa4a23b64acd8d707b4b3a011cf3d3ef3ea4ed68aef86d1d556325c7a
Tx public key: 86fedcd1cc1b245031054849c13cd1500fff77d4cb157cd568c50e5c63ca3af1
Timestamp: 1752913720 Timestamp [UCT]: 2025-07-19 08:28:40 Age [y:d:h:m:s]: 00:125:06:14:07
Block: 1328702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88312 RingCT/type: yes/0
Extra: 0186fedcd1cc1b245031054849c13cd1500fff77d4cb157cd568c50e5c63ca3af1021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e99d6f23f7c7a39343e7e68e290f6c132a8ce69fbe0b46aa9dd7e2cdb20ca4e 0.600000000000 1816465 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": 1328712, "vin": [ { "gen": { "height": 1328702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e99d6f23f7c7a39343e7e68e290f6c132a8ce69fbe0b46aa9dd7e2cdb20ca4e" } } ], "extra": [ 1, 134, 254, 220, 209, 204, 27, 36, 80, 49, 5, 72, 73, 193, 60, 209, 80, 15, 255, 119, 212, 203, 21, 124, 213, 104, 197, 14, 92, 99, 202, 58, 241, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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