← previous blocknext block →recent activity
Analyzing
Block #106,552,288
18 transactions · 17 stateful · 2026-09-20 19:56:40 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,552,288 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w26w07w08w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef5959a3…2a2f
0x34b655…2a6f
4 touches
1 conflict
0x57c59b92…6b86
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x906eae3c…27fa
0x34b655…2a6f
4 touches
1 conflict
0xa35509fa…5cb3
0x34b655…2a6f
4 touches
1 conflict
0xa579bcf9…8820
0x34b655…2a6f
4 touches
1 conflict
0xaa3b4402…74e6
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
1 conflict on slot 0xef5959a35a…d32a2f
Audit this contract →
← previous block·next block →recent activity