Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6491023e3ec9b62e4fbad9e5809aab30bb1a0711c69a7b99ea803d6bd8baeb71

Tx prefix hash: 3433d1be649271db85268bb9370c61315038e5141bf1b976f9535881cfb5716f
Tx public key: 7ba50f63d0b64e0437b9a77325ab8415173e73347cf74da4c2ea92e19b9d9f6f
Timestamp: 1708487180 Timestamp [UCT]: 2024-02-21 03:46:20 Age [y:d:h:m:s]: 01:005:01:49:04
Block: 962106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264616 RingCT/type: yes/0
Extra: 017ba50f63d0b64e0437b9a77325ab8415173e73347cf74da4c2ea92e19b9d9f6f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43e76b4f97000ef2ce769e963363966b17c64deb49f2a45968b101c1a031aee0 0.600000000000 1421729 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": 962116, "vin": [ { "gen": { "height": 962106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43e76b4f97000ef2ce769e963363966b17c64deb49f2a45968b101c1a031aee0" } } ], "extra": [ 1, 123, 165, 15, 99, 208, 182, 78, 4, 55, 185, 167, 115, 37, 171, 132, 21, 23, 62, 115, 52, 124, 247, 77, 164, 194, 234, 146, 225, 155, 157, 159, 111, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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