Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a57a2aff0b24fc6928fc84fec5f4ff305b97357a3b79feb5ae534a3773a1be5

Tx prefix hash: d3966af794d9d8e8541c9ef5d15fa87e3d39810698fb1c3de9d9408a7924af66
Tx public key: e585b8275f46334cde1473c26b35747c3dbd692fb1a96d3e1619a966068c84a4
Timestamp: 1730768402 Timestamp [UCT]: 2024-11-05 01:00:02 Age [y:d:h:m:s]: 00:143:15:59:33
Block: 1146740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102512 RingCT/type: yes/0
Extra: 01e585b8275f46334cde1473c26b35747c3dbd692fb1a96d3e1619a966068c84a4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c0657cea4f78fe52f4fc3e04b820e100ead937751e987a652dda7b1cf86f443 0.600000000000 1631431 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": 1146750, "vin": [ { "gen": { "height": 1146740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c0657cea4f78fe52f4fc3e04b820e100ead937751e987a652dda7b1cf86f443" } } ], "extra": [ 1, 229, 133, 184, 39, 95, 70, 51, 76, 222, 20, 115, 194, 107, 53, 116, 124, 61, 189, 105, 47, 177, 169, 109, 62, 22, 25, 169, 102, 6, 140, 132, 164, 2, 17, 0, 0, 0, 3, 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