Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6633c1562107495d967d10f920c155a581c3b20933e00c65a69eed979bc0bbde

Tx prefix hash: fdd0e3480994becf01e1dc2d493271a52040c591f04c5f301f96276a9cce6387
Tx public key: 18d022c2a223acba505bedec5a3efef56a9f771f71c0a6ae18eda7c92038a0f9
Timestamp: 1713284328 Timestamp [UCT]: 2024-04-16 16:18:48 Age [y:d:h:m:s]: 00:256:00:03:52
Block: 1001859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183263 RingCT/type: yes/0
Extra: 0118d022c2a223acba505bedec5a3efef56a9f771f71c0a6ae18eda7c92038a0f902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b044dfe779d57a3eaf144f155b2b317045e7f2a98663af657b48c7fec1515ff7 0.600000000000 1462371 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": 1001869, "vin": [ { "gen": { "height": 1001859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b044dfe779d57a3eaf144f155b2b317045e7f2a98663af657b48c7fec1515ff7" } } ], "extra": [ 1, 24, 208, 34, 194, 162, 35, 172, 186, 80, 91, 237, 236, 90, 62, 254, 245, 106, 159, 119, 31, 113, 192, 166, 174, 24, 237, 167, 201, 32, 56, 160, 249, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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