Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb87246d9035a21fe78846d8b0e5da1b16d45d318a94753dab10950b4862c39c

Tx prefix hash: 85fae2c64531241699c5db43c1b3297715b73e4b9eea73aaccb78ffed9dea4e9
Tx public key: 3243ce988ed93a04d6c9f1109c8b915d8d44c13a203581f46ea87a4459bd75f7
Timestamp: 1751635528 Timestamp [UCT]: 2025-07-04 13:25:28 Age [y:d:h:m:s]: 00:133:10:12:32
Block: 1318629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93648 RingCT/type: yes/0
Extra: 013243ce988ed93a04d6c9f1109c8b915d8d44c13a203581f46ea87a4459bd75f702110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78876bdb647fd9d04880a9b72bc75b6ad2cd8cb22b8759f4119b94995e698a70 0.600000000000 1806314 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": 1318639, "vin": [ { "gen": { "height": 1318629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78876bdb647fd9d04880a9b72bc75b6ad2cd8cb22b8759f4119b94995e698a70" } } ], "extra": [ 1, 50, 67, 206, 152, 142, 217, 58, 4, 214, 201, 241, 16, 156, 139, 145, 93, 141, 68, 193, 58, 32, 53, 129, 244, 110, 168, 122, 68, 89, 189, 117, 247, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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