← previous blocknext block →recent activity
Analyzing
Block #98,563,835
12 transactions · 11 stateful · 2026-08-23 19:48:16 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,563,835 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3592eda…27d8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xb4b350eb…8c96
0x34b655…2a6f
4 touches
1 conflict
0x438f4336…47c9
0x34b655…2a6f
2 touches
0 conflicts
0x57676b36…5d4f
0x34b655…2a6f
2 touches
0 conflicts
0x5d6e47d8…9ca5
0x34b655…2a6f
2 touches
0 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xf3592eda1f…d427d8
Audit this contract →
← previous block·next block →recent activity