Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 600d596aa4b23c0329126e655ff05f05a1266313f5ab4886cf400c8b34d414f9

Tx prefix hash: d08c98467942456bd938d4b732e60cf2d95667e0fb4270a763a3e254c6d5d99c
Tx public key: f3ce69bda5acc29bba94c9eeb6ccd616deeeb3778dc7b315c961341d69d3faac
Timestamp: 1702777163 Timestamp [UCT]: 2023-12-17 01:39:23 Age [y:d:h:m:s]: 01:099:09:53:12
Block: 914767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332174 RingCT/type: yes/0
Extra: 01f3ce69bda5acc29bba94c9eeb6ccd616deeeb3778dc7b315c961341d69d3faac02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71f0075f3fdd65e177099939a0bb6a676b0e4b7468041fec302ceb04ec1059d7 0.600000000000 1372119 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": 914777, "vin": [ { "gen": { "height": 914767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71f0075f3fdd65e177099939a0bb6a676b0e4b7468041fec302ceb04ec1059d7" } } ], "extra": [ 1, 243, 206, 105, 189, 165, 172, 194, 155, 186, 148, 201, 238, 182, 204, 214, 22, 222, 238, 179, 119, 141, 199, 179, 21, 201, 97, 52, 29, 105, 211, 250, 172, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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