Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5532a5ddf50fa9b89f81f66b8d8ba8aad15001728af8a73ad87e8ce5c5dc0d7

Tx prefix hash: bfe6a12be441190954757d919a181ab8f700abef19ce1fd060304d2b6ae3ad54
Tx public key: d4febc8b65b8c36cff9e66298ceb965f1ae18f0eb5ddaca61070da255771034c
Timestamp: 1724565133 Timestamp [UCT]: 2024-08-25 05:52:13 Age [y:d:h:m:s]: 01:074:18:46:19
Block: 1095408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311885 RingCT/type: yes/0
Extra: 01d4febc8b65b8c36cff9e66298ceb965f1ae18f0eb5ddaca61070da255771034c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df01b18424d2626015a6b0d0aad1045f807d51c7240e08c0fc6e7ca9a95b23d6 0.600000000000 1570579 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": 1095418, "vin": [ { "gen": { "height": 1095408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df01b18424d2626015a6b0d0aad1045f807d51c7240e08c0fc6e7ca9a95b23d6" } } ], "extra": [ 1, 212, 254, 188, 139, 101, 184, 195, 108, 255, 158, 102, 41, 140, 235, 150, 95, 26, 225, 143, 14, 181, 221, 172, 166, 16, 112, 218, 37, 87, 113, 3, 76, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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