← previous blocknext block →recent activity
Analyzing
Block #105,538,724
16 transactions · 16 stateful · 2026-09-17 06:52:54 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,538,724 · 16 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
2w03w14w09w111w212w213w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4188cc5f…2d2e
0x34b655…2a6f
8 touches
6 conflicts
0xeaf0ccf5…3957
0x34b655…2a6f
8 touches
6 conflicts
0xf36124ad…c08f
0x34b655…2a6f
4 touches
1 conflict
0x6b595a5d…894c
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0xa5390204…06e7
0x34b655…2a6f
4 touches
1 conflict
0xb6ed511f…6b68
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 0x4188cc5f13…782d2e
Audit this contract →
← previous block·next block →recent activity