Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07f8b2df814feaa74dbcb91d9412c685fbf07d68b8d22298c46d8ca8515dfb98

Tx prefix hash: a5a4da0009daf54ad88150fd69df34facd38dba3d5d1b71a820f23f41c6694b7
Tx public key: eed382f2273f4268a92f7819bae6d3551e8ce85ccc2e8e350d29ddec6e1754f5
Timestamp: 1751144337 Timestamp [UCT]: 2025-06-28 20:58:57 Age [y:d:h:m:s]: 00:145:01:00:35
Block: 1314758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101760 RingCT/type: yes/0
Extra: 01eed382f2273f4268a92f7819bae6d3551e8ce85ccc2e8e350d29ddec6e1754f5021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e164379bd9629dcbf76a93c2ff4030c96d6c39d6b76bcf031299e01c1da68339 0.600000000000 1802409 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": 1314768, "vin": [ { "gen": { "height": 1314758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e164379bd9629dcbf76a93c2ff4030c96d6c39d6b76bcf031299e01c1da68339" } } ], "extra": [ 1, 238, 211, 130, 242, 39, 63, 66, 104, 169, 47, 120, 25, 186, 230, 211, 85, 30, 140, 232, 92, 204, 46, 142, 53, 13, 41, 221, 236, 110, 23, 84, 245, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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