Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15190dcf94f8974825c6705b122b49e46b53eb292fd7449ee6bc7d9d6783c1d8

Tx prefix hash: 4f6b31e660caa6253e685b904d440551370a52dc5c9156888e11a1779792ddf2
Tx public key: 438c7b4ca0e5247d122dff3bcb964f9345793f079ddf67fd9661a7ceca1011ab
Timestamp: 1721665479 Timestamp [UCT]: 2024-07-22 16:24:39 Age [y:d:h:m:s]: 00:296:11:14:48
Block: 1071347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211837 RingCT/type: yes/0
Extra: 01438c7b4ca0e5247d122dff3bcb964f9345793f079ddf67fd9661a7ceca1011ab021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97701295b2f18ab3a88d7cdb064fb0c0bfcd5e0fb434f6bc48c6fffb665e3dd4 0.600000000000 1543540 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": 1071357, "vin": [ { "gen": { "height": 1071347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97701295b2f18ab3a88d7cdb064fb0c0bfcd5e0fb434f6bc48c6fffb665e3dd4" } } ], "extra": [ 1, 67, 140, 123, 76, 160, 229, 36, 125, 18, 45, 255, 59, 203, 150, 79, 147, 69, 121, 63, 7, 157, 223, 103, 253, 150, 97, 167, 206, 202, 16, 17, 171, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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