← previous blocknext block →recent activity
Analyzing
Block #96,035,798
16 transactions · 16 stateful · 2026-08-14 22:24:50 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,035,798 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a5ced1c…3b29
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x02991b41…19e6
0x34b655…2a6f
8 touches
6 conflicts
0xbfd33a92…5c35
0x34b655…2a6f
6 touches
3 conflicts
0x65f773b6…46cc
0x34b655…2a6f
4 touches
1 conflict
0xef3f5637…f47c
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
10 conflicts on slot 0x8a5ced1cae…443b29
Audit this contract →
← previous block·next block →recent activity