← previous blocknext block →recent activity
Analyzing
Block #106,403,249
30 transactions · 27 stateful · 2026-09-20 07:26:31 UTC
Parallelism
87/100
Blocked
52%
Avg conflicts / tx
1.03
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,403,249 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w06w19w014w316w218w320w122w023w124w225w327w128w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xedf0fd5d…0c8b
0x34b655…2a6f
8 touches
6 conflicts
0x2029b74e…c206
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
8 touches
6 conflicts
0x216e939a…fce2
0x5be4ee…673f
7 touches
6 conflicts
0x216e939a…fcd4
0x5be4ee…673f
7 touches
6 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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity