← previous blocknext block →recent activity
Analyzing
Block #105,868,916
12 transactions · 12 stateful · 2026-09-18 10:36:16 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,868,916 · 12 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
7w08w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0x5e4ed8fb…2d93
0x34b655…2a6f
4 touches
1 conflict
0xd488e0a9…9bae
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x23529e13…6f25
0x34b655…2a6f
4 touches
1 conflict
0x2be506d4…d10a
0x34b655…2a6f
2 touches
0 conflicts
0x3e39ff1b…648b
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 0x4abfb3894a…c318f4
Audit this contract →
← previous block·next block →recent activity