Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 050185cd967cd764f782de177f3f016558e45a3ea1e8b600c93796c1e85be11a

Tx prefix hash: 5de2bf3f2a2e8711994f0edefb3eb2b9977d78225b019110dc428b8b658b8edf
Tx public key: 1f8a3f4cd80bb327ef824e42e1c6885a3494ec6d441024ef32a69ca3ecde1d77
Timestamp: 1734420258 Timestamp [UCT]: 2024-12-17 07:24:18 Age [y:d:h:m:s]: 00:093:18:44:00
Block: 1177015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66805 RingCT/type: yes/0
Extra: 011f8a3f4cd80bb327ef824e42e1c6885a3494ec6d441024ef32a69ca3ecde1d77021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40be683dcc225b4daea99237dc228b6c6a7e582f5db5be338c96ad5157323983 0.600000000000 1663376 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": 1177025, "vin": [ { "gen": { "height": 1177015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40be683dcc225b4daea99237dc228b6c6a7e582f5db5be338c96ad5157323983" } } ], "extra": [ 1, 31, 138, 63, 76, 216, 11, 179, 39, 239, 130, 78, 66, 225, 198, 136, 90, 52, 148, 236, 109, 68, 16, 36, 239, 50, 166, 156, 163, 236, 222, 29, 119, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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