Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4430ac41fe4fdef577255fd13b4f030222ae27fd590d1f81f1b4ac6c28475ca8

Tx prefix hash: d4ee940ff04d00ff37df55ddd3d84c6b72a74ec3bef9717aed1710ec67b0028a
Tx public key: 3d335f9fd3bf3122527565bd873cc9e559ca2a6f2d531e0909f73d2dbaf69bd2
Timestamp: 1710514295 Timestamp [UCT]: 2024-03-15 14:51:35 Age [y:d:h:m:s]: 01:019:08:30:30
Block: 978932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274797 RingCT/type: yes/0
Extra: 013d335f9fd3bf3122527565bd873cc9e559ca2a6f2d531e0909f73d2dbaf69bd20211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82764f638b7413ff73b606b1259a8a425efd66344bc46e927b2906180cbb93bc 0.600000000000 1438961 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": 978942, "vin": [ { "gen": { "height": 978932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82764f638b7413ff73b606b1259a8a425efd66344bc46e927b2906180cbb93bc" } } ], "extra": [ 1, 61, 51, 95, 159, 211, 191, 49, 34, 82, 117, 101, 189, 135, 60, 201, 229, 89, 202, 42, 111, 45, 83, 30, 9, 9, 247, 61, 45, 186, 246, 155, 210, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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