Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9271ca310986e8df488300d2a8e78f999f739a4b6122f60351854e4d863844b3

Tx prefix hash: c7c94dd32815e25892a9d60f03da926e5abc3e14768c5098391862bef34aab7c
Tx public key: a1d91a4032f1acf626455d40b6343432cad6ce41f7bff53253ccc9dc9c321eaa
Timestamp: 1711334555 Timestamp [UCT]: 2024-03-25 02:42:35 Age [y:d:h:m:s]: 00:296:00:14:44
Block: 985736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211866 RingCT/type: yes/0
Extra: 01a1d91a4032f1acf626455d40b6343432cad6ce41f7bff53253ccc9dc9c321eaa0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d22f607f05f894401e4438752b7f9c4e294a555db22bdc770e6ea685d3734495 0.600000000000 1445953 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": 985746, "vin": [ { "gen": { "height": 985736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d22f607f05f894401e4438752b7f9c4e294a555db22bdc770e6ea685d3734495" } } ], "extra": [ 1, 161, 217, 26, 64, 50, 241, 172, 246, 38, 69, 93, 64, 182, 52, 52, 50, 202, 214, 206, 65, 247, 191, 245, 50, 83, 204, 201, 220, 156, 50, 30, 170, 2, 17, 0, 0, 0, 2, 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