Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39cf55292c4f4c6bde4c43f3535de7fc41c7f67cede459380accb9f1e6b1446f

Tx prefix hash: b95b374091445f4e2dc88b9ab8830b2b95f7dea3ece11091b5715463990f9462
Tx public key: e91e6dd34da753890d25652ed6dc65f0858a9621d69bc39777ef47ebfa5a1e7a
Timestamp: 1632285052 Timestamp [UCT]: 2021-09-22 04:30:52 Age [y:d:h:m:s]: 03:047:06:42:50
Block: 338567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 809915 RingCT/type: yes/0
Extra: 01e91e6dd34da753890d25652ed6dc65f0858a9621d69bc39777ef47ebfa5a1e7a02110000000a8d0de867000000000000000000

1 output(s) for total of 46.364696087000 dcy

stealth address amount amount idx
00: 4877af368c35af8b1a86d56d6419cf15a2efe3785f0d4a312e310727f6113168 46.364696087000 696736 of 0

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": 338577, "vin": [ { "gen": { "height": 338567 } } ], "vout": [ { "amount": 46364696087, "target": { "key": "4877af368c35af8b1a86d56d6419cf15a2efe3785f0d4a312e310727f6113168" } } ], "extra": [ 1, 233, 30, 109, 211, 77, 167, 83, 137, 13, 37, 101, 46, 214, 220, 101, 240, 133, 138, 150, 33, 214, 155, 195, 151, 119, 239, 71, 235, 250, 90, 30, 122, 2, 17, 0, 0, 0, 10, 141, 13, 232, 103, 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