← previous blocknext block →recent activity
Analyzing
Block #98,527,116
16 transactions · 14 stateful · 2026-08-23 16:36:43 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,527,116 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w09w210w312w114w015w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x307d7327…3971
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xcd1306ad…f1b8
0x34b655…2a6f
6 touches
3 conflicts
0x065ff70b…356d
0x40c49f…2af0
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0x41469894…5990
0x34b655…2a6f
4 touches
1 conflict
0x4ccfe55c…de03
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
3 conflicts on slot 0x307d73272e…793971
Audit this contract →
← previous block·next block →recent activity