← previous blocknext block →recent activity
Analyzing
Block #107,839,050
22 transactions · 16 stateful · 2026-09-25 07:56:45 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,839,050 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w210w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x31d88d27…7617
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xdcd07321…1c31
0x34b655…2a6f
6 touches
3 conflicts
0x3aed9088…e43c
0x34b655…2a6f
4 touches
1 conflict
0x44b34ec4…e444
0x34b655…2a6f
4 touches
1 conflict
0x481db2dd…cc35
0x34b655…2a6f
4 touches
1 conflict
0x7fde764b…02b4
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity