Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71d46c11c67b9171b011955752b47dbba9a5e2ea2f044c4b0c3dee566545ed41

Tx prefix hash: c38120e819329179b2c783fc78fdf31d58a995e1a48186f9f6023184f24e9bad
Tx public key: 0118d4377be5641d103065d7efa693be455dddb08bd6cb3eb86f4b4b113e2f00
Timestamp: 1707143663 Timestamp [UCT]: 2024-02-05 14:34:23 Age [y:d:h:m:s]: 01:088:23:46:32
Block: 950956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324682 RingCT/type: yes/0
Extra: 010118d4377be5641d103065d7efa693be455dddb08bd6cb3eb86f4b4b113e2f000211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59eb0d53049996d7d96c9964d4bdf760fdc51eff430f86ce0d31e92aeb21bfcf 0.600000000000 1409654 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": 950966, "vin": [ { "gen": { "height": 950956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59eb0d53049996d7d96c9964d4bdf760fdc51eff430f86ce0d31e92aeb21bfcf" } } ], "extra": [ 1, 1, 24, 212, 55, 123, 229, 100, 29, 16, 48, 101, 215, 239, 166, 147, 190, 69, 93, 221, 176, 139, 214, 203, 62, 184, 111, 75, 75, 17, 62, 47, 0, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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