Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0088c7864f2c2aff032b46785b02565a6c20fc9b75457471417770b145e19a93

Tx prefix hash: 983c98cc8dad7c485afffb0a65fb34bd8b568cceaaba5dba708a1a53d8c19837
Tx public key: 794b06a3221f6c5a1b0eb2bec6b34e9c186a42defdc72dd84df2c10ce161e2c6
Timestamp: 1754350997 Timestamp [UCT]: 2025-08-04 23:43:17 Age [y:d:h:m:s]: 00:108:12:18:21
Block: 1340400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76534 RingCT/type: yes/0
Extra: 01794b06a3221f6c5a1b0eb2bec6b34e9c186a42defdc72dd84df2c10ce161e2c6021100000010ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91bb9129ffd8091db9ed41af59f2be8a6c214505f7887816344b90a0dd3a4816 0.600000000000 1828217 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": 1340410, "vin": [ { "gen": { "height": 1340400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91bb9129ffd8091db9ed41af59f2be8a6c214505f7887816344b90a0dd3a4816" } } ], "extra": [ 1, 121, 75, 6, 163, 34, 31, 108, 90, 27, 14, 178, 190, 198, 179, 78, 156, 24, 106, 66, 222, 253, 199, 45, 216, 77, 242, 193, 12, 225, 97, 226, 198, 2, 17, 0, 0, 0, 16, 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