Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38f6082188ab2aa2ff359b2d24bf1f8fb15a54ea3f63ad19f4e734485dd89998

Tx prefix hash: bb4a3dd3a08300a677d0ecdc807686638059ae3e8cdd051e071d13d0f29d199d
Tx public key: 9ea6ee4ffe256cffdf287c60d4743ca432d95e6dd08225c3a03a9919213c3d41
Timestamp: 1755170776 Timestamp [UCT]: 2025-08-14 11:26:16 Age [y:d:h:m:s]: 00:051:13:25:03
Block: 1346627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36326 RingCT/type: yes/0
Extra: 019ea6ee4ffe256cffdf287c60d4743ca432d95e6dd08225c3a03a9919213c3d410211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 915b340555b573a4901b9f937ba3c7ce40925cc2e3811a03f969f929971bd26d 0.600000000000 1834528 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": 1346637, "vin": [ { "gen": { "height": 1346627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "915b340555b573a4901b9f937ba3c7ce40925cc2e3811a03f969f929971bd26d" } } ], "extra": [ 1, 158, 166, 238, 79, 254, 37, 108, 255, 223, 40, 124, 96, 212, 116, 60, 164, 50, 217, 94, 109, 208, 130, 37, 195, 160, 58, 153, 25, 33, 60, 61, 65, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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