Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac83dc080f9953873d19f67d5294e0bb379d13c0226aa2c3101c834f1be57dfd

Tx prefix hash: 60edfdc93ca0c58719b3173fcf26c61c9707f69d11a14e7565a3cd63bb118746
Tx public key: fc2a20ec7a1666d7893b744b42ff7fb0b6869ee84c49ef7e635a31b87bb6b887
Timestamp: 1681378889 Timestamp [UCT]: 2023-04-13 09:41:29 Age [y:d:h:m:s]: 01:361:02:21:35
Block: 737601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519360 RingCT/type: yes/0
Extra: 01fc2a20ec7a1666d7893b744b42ff7fb0b6869ee84c49ef7e635a31b87bb6b8870211000000015029cbac000000000000000000

1 output(s) for total of 2.208116157000 dcy

stealth address amount amount idx
00: 1ea9f2e7d6d3be10f5287b0f3424f0db4271ce5461972de6ef7c36db1c0ec0b8 2.208116157000 1184180 of 0

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": 737611, "vin": [ { "gen": { "height": 737601 } } ], "vout": [ { "amount": 2208116157, "target": { "key": "1ea9f2e7d6d3be10f5287b0f3424f0db4271ce5461972de6ef7c36db1c0ec0b8" } } ], "extra": [ 1, 252, 42, 32, 236, 122, 22, 102, 215, 137, 59, 116, 75, 66, 255, 127, 176, 182, 134, 158, 232, 76, 73, 239, 126, 99, 90, 49, 184, 123, 182, 184, 135, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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