← previous blocknext block →recent activity
Analyzing
Block #106,921,740
19 transactions · 19 stateful · 2026-09-22 02:57:09 UTC
Parallelism
74/100
Blocked
42%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,921,740 · 19 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
1w02w13w04w05w06w17w28w09w310w414w115w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8c615d4…5da3
0x34b655…2a6f
8 touches
6 conflicts
0x8e879690…725e
0x34b655…2a6f
6 touches
3 conflicts
0xe3425a1e…da15
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0x7dd96c96…7335
0x34b655…2a6f
4 touches
1 conflict
0x8cc18498…ce7e
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
6 conflicts on slot 0xc8c615d41e…025da3
Audit this contract →
← previous block·next block →recent activity