← previous blocknext block →recent activity
Analyzing
Block #106,419,995
18 transactions · 18 stateful · 2026-09-20 08:50:48 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,419,995 · 18 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
1w05w17w08w19w210w111w212w316w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf171f918…801d
0x34b655…2a6f
4 touches
1 conflict
0x00ccd5e9…d14b
0x34b655…2a6f
4 touches
1 conflict
0x0acbae3f…9d02
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x200c7bcc…807c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0xf6deafb553…9e5c25
Audit this contract →
← previous block·next block →recent activity