← previous blocknext block →recent activity
Analyzing
Block #107,841,339
19 transactions · 18 stateful · 2026-09-25 08:08:17 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,841,339 · 19 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
1w05w18w09w010w111w212w313w414w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d64635b…18e5
0x34b655…2a6f
8 touches
6 conflicts
0x3ff9db2e…22f6
0x34b655…2a6f
8 touches
6 conflicts
0x31b513ff…b247
0x34b655…2a6f
6 touches
3 conflicts
0xb6039eff…b0d1
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
4 touches
1 conflict
0x44b4869a…fe59
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 0x4d64635b7e…1a18e5
Audit this contract →
← previous block·next block →recent activity