Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9cf491884693d36b16e009522ef2e1232403699b7ad4c4ec63d93cb63d3150b

Tx prefix hash: 5b77addbe891b2b7f0bb84666e43a5ad2beb59b3904cb3cf852b919fbf8dd009
Tx public key: 232e952d7f72375c485612b8fc019e3691709d697c1fb16ae664fd4cddadb5c5
Timestamp: 1716202048 Timestamp [UCT]: 2024-05-20 10:47:28 Age [y:d:h:m:s]: 00:282:03:34:29
Block: 1026072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201634 RingCT/type: yes/0
Extra: 01232e952d7f72375c485612b8fc019e3691709d697c1fb16ae664fd4cddadb5c50211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69c5364290cea798d4a7dc29df23fc06e95b91624cb174aae4cab309787d4f07 0.600000000000 1492957 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": 1026082, "vin": [ { "gen": { "height": 1026072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69c5364290cea798d4a7dc29df23fc06e95b91624cb174aae4cab309787d4f07" } } ], "extra": [ 1, 35, 46, 149, 45, 127, 114, 55, 92, 72, 86, 18, 184, 252, 1, 158, 54, 145, 112, 157, 105, 124, 31, 177, 106, 230, 100, 253, 76, 221, 173, 181, 197, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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