Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f61670060b3a972a439038836821d0012dc15fd5e054d450adf211b47470c167

Tx prefix hash: 77abc42a36da3d420ec3dfcfab54072fb8da3223c901ca1e5d2fab7ebc9e4b06
Tx public key: eef421cae47bc7cb524b302e8d41598d0c39de892678a198990ec9c535e646c8
Timestamp: 1705847275 Timestamp [UCT]: 2024-01-21 14:27:55 Age [y:d:h:m:s]: 01:291:23:35:30
Block: 940193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467501 RingCT/type: yes/0
Extra: 01eef421cae47bc7cb524b302e8d41598d0c39de892678a198990ec9c535e646c802110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02f4b6fcf516a8bd5ddb70dd0027353638b5eb8efb6c20805398cf7413850a42 0.600000000000 1398327 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": 940203, "vin": [ { "gen": { "height": 940193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02f4b6fcf516a8bd5ddb70dd0027353638b5eb8efb6c20805398cf7413850a42" } } ], "extra": [ 1, 238, 244, 33, 202, 228, 123, 199, 203, 82, 75, 48, 46, 141, 65, 89, 141, 12, 57, 222, 137, 38, 120, 161, 152, 153, 14, 201, 197, 53, 230, 70, 200, 2, 17, 0, 0, 0, 7, 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