← previous blocknext block →recent activity
Analyzing
Block #105,845,571
19 transactions · 18 stateful · 2026-09-18 08:38:47 UTC
Parallelism
63/100
Blocked
39%
Avg conflicts / tx
0.89
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,845,571 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w19w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc40fa8a7…a319
0x34b655…2a6f
12 touches
15 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
10 touches
10 conflicts
0xf788c790…e66f
0x34b655…2a6f
8 touches
6 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
6 touches
3 conflicts
0x2f662f0a…f602
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x6237b89c…9779
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
15 conflicts on slot 0xc40fa8a7a4…d2a319
Audit this contract →
← previous block·next block →recent activity