Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0817691ff8a31c9d14e36f9050bfed66048eb7471b2dcf22e5bf46c4461552f

Tx prefix hash: 8f525419d5c32260ec0cef20b04cebd6eb82c3b939865fc89f71f40e277a301a
Tx public key: d3cb1bf93409997aa273a16919f71fa5f5fd595d5b08b5a54352001d87d0fbb7
Timestamp: 1731023582 Timestamp [UCT]: 2024-11-07 23:53:02 Age [y:d:h:m:s]: 00:170:23:05:13
Block: 1148859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122035 RingCT/type: yes/0
Extra: 01d3cb1bf93409997aa273a16919f71fa5f5fd595d5b08b5a54352001d87d0fbb7021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c25870856aff643a57400d98d827e0d01d744d055d616e78ce75613d7b55c75 0.600000000000 1633804 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": 1148869, "vin": [ { "gen": { "height": 1148859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c25870856aff643a57400d98d827e0d01d744d055d616e78ce75613d7b55c75" } } ], "extra": [ 1, 211, 203, 27, 249, 52, 9, 153, 122, 162, 115, 161, 105, 25, 247, 31, 165, 245, 253, 89, 93, 91, 8, 181, 165, 67, 82, 0, 29, 135, 208, 251, 183, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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