← previous blocknext block →recent activity
Analyzing
Block #105,881,343
24 transactions · 20 stateful · 2026-09-18 11:38:48 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,881,343 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w014w115w116w217w318w419w523w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb02db78…56cb
0x34b655…2a6f
12 touches
15 conflicts
0x18978822…2623
0x34b655…2a6f
10 touches
10 conflicts
0x4abfb389…18f4
0x34b655…2a6f
8 touches
6 conflicts
0x297de2d5…7396
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x7bf4ea6c…3cdc
0x34b655…2a6f
4 touches
1 conflict
0xd79c9727…1233
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
15 conflicts on slot 0xfb02db7805…5656cb
Audit this contract →
← previous block·next block →recent activity