Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3ef628c7946c12640632be002ef26dfbda7b672cfc9c21beb8bd84b3b4c2a2b

Tx prefix hash: ba47b7c4fded362651adacbbcb2e085785e6521b9cbc4cd547af4b85bf4990f4
Tx public key: 9770f00a683f06e1f91a33d3a62323f567a252ae0c4f7c0a7f21e3b1cc54b87b
Timestamp: 1698501846 Timestamp [UCT]: 2023-10-28 14:04:06 Age [y:d:h:m:s]: 02:019:20:17:07
Block: 879542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 533770 RingCT/type: yes/0
Extra: 019770f00a683f06e1f91a33d3a62323f567a252ae0c4f7c0a7f21e3b1cc54b87b021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.747673954000 dcy

stealth address amount amount idx
00: b810d4491814c8472a9eca6442c6b150d5ad6ac745640970deed0b9261f4b688 0.747673954000 1335070 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": 879552, "vin": [ { "gen": { "height": 879542 } } ], "vout": [ { "amount": 747673954, "target": { "key": "b810d4491814c8472a9eca6442c6b150d5ad6ac745640970deed0b9261f4b688" } } ], "extra": [ 1, 151, 112, 240, 10, 104, 63, 6, 225, 249, 26, 51, 211, 166, 35, 35, 245, 103, 162, 82, 174, 12, 79, 124, 10, 127, 33, 227, 177, 204, 84, 184, 123, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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