Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96e1c62f7a9e4b4993f71f595ee7b45c083c9e48288eafb4f8404a28e01b459e

Tx prefix hash: 09096ab1103681cb91d6609c9ce5c0039961452647936c1c9648284f2b5a9ad5
Tx public key: e03ac9f58c05c9aa601ad112c372531bf45ae14fec6b791cbdba4b206cab8897
Timestamp: 1711357946 Timestamp [UCT]: 2024-03-25 09:12:26 Age [y:d:h:m:s]: 01:240:16:19:56
Block: 985935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430681 RingCT/type: yes/0
Extra: 01e03ac9f58c05c9aa601ad112c372531bf45ae14fec6b791cbdba4b206cab88970211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6aa308627b3775aebb94a10a55fc9113c46b4f1eb0ec95fb3df841ca463a77c 0.600000000000 1446156 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": 985945, "vin": [ { "gen": { "height": 985935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6aa308627b3775aebb94a10a55fc9113c46b4f1eb0ec95fb3df841ca463a77c" } } ], "extra": [ 1, 224, 58, 201, 245, 140, 5, 201, 170, 96, 26, 209, 18, 195, 114, 83, 27, 244, 90, 225, 79, 236, 107, 121, 28, 189, 186, 75, 32, 108, 171, 136, 151, 2, 17, 0, 0, 0, 1, 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