Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1900923aeb38a3f71b1776007afcbc4423cb73c1705669c0811fa08383cba4df

Tx prefix hash: 975862346026fa4d9f953283f69774017aee9a3bc425e7b2eebfd9bd11e2980d
Tx public key: 40eb8dee7d68d0cb0b540e044aa9b33b445e1356fa6ebed5638fb7ee5ec99623
Timestamp: 1632169592 Timestamp [UCT]: 2021-09-20 20:26:32 Age [y:d:h:m:s]: 03:244:22:47:06
Block: 337764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 950912 RingCT/type: yes/0
Extra: 0140eb8dee7d68d0cb0b540e044aa9b33b445e1356fa6ebed5638fb7ee5ec9962302110000005536fe6557000000000000000000

1 output(s) for total of 46.649617906000 dcy

stealth address amount amount idx
00: 3ab0e66d01407664acc2ffaca274b4dca3141df14791dc8a57f18753a3c32d80 46.649617906000 695385 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": 337774, "vin": [ { "gen": { "height": 337764 } } ], "vout": [ { "amount": 46649617906, "target": { "key": "3ab0e66d01407664acc2ffaca274b4dca3141df14791dc8a57f18753a3c32d80" } } ], "extra": [ 1, 64, 235, 141, 238, 125, 104, 208, 203, 11, 84, 14, 4, 74, 169, 179, 59, 68, 94, 19, 86, 250, 110, 190, 213, 99, 143, 183, 238, 94, 201, 150, 35, 2, 17, 0, 0, 0, 85, 54, 254, 101, 87, 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