Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11f7e66e096df5ae20b4cef0167efd9ca4351f3746a2b195d3559d963e65367f

Tx prefix hash: 8b3e23ce7fe62cef56c4fe0b59d67543320e3e2a157dc91d1cf2f237e016e828
Tx public key: ac30a2887c518d3487e7d68d96e40c79335d4deed22454b6ed92330572815f42
Timestamp: 1749271696 Timestamp [UCT]: 2025-06-07 04:48:16 Age [y:d:h:m:s]: 00:161:23:45:54
Block: 1299681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113458 RingCT/type: yes/0
Extra: 01ac30a2887c518d3487e7d68d96e40c79335d4deed22454b6ed92330572815f4202110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38b8a79981aa72f32bd7a2ab64e7b4aa3cf91800c1ffadf8421e75e125d61b0f 0.600000000000 1787218 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": 1299691, "vin": [ { "gen": { "height": 1299681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38b8a79981aa72f32bd7a2ab64e7b4aa3cf91800c1ffadf8421e75e125d61b0f" } } ], "extra": [ 1, 172, 48, 162, 136, 124, 81, 141, 52, 135, 231, 214, 141, 150, 228, 12, 121, 51, 93, 77, 238, 210, 36, 84, 182, 237, 146, 51, 5, 114, 129, 95, 66, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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