← previous blocknext block →recent activity
Analyzing
Block #105,608,011
17 transactions · 15 stateful · 2026-09-17 12:41:39 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,608,011 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w010w114w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8d31c56…91df
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
0x34b655…2a6f
4 touches
1 conflict
0x2d7bc277…e916
0x34b655…2a6f
2 touches
0 conflicts
0x33b5035a…d1c6
0x34b655…2a6f
2 touches
0 conflicts
0x687f25fe…1fba
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc8d31c5659…f691df
Audit this contract →
← previous block·next block →recent activity