← previous blocknext block →recent activity
Analyzing
Block #106,004,578
20 transactions · 19 stateful · 2026-09-18 22:00:06 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,004,578 · 20 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
1w03w04w16w07w18w29w310w416w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e9a3afd…a6e5
0x34b655…2a6f
10 touches
10 conflicts
0x347abf57…4b86
0x34b655…2a6f
10 touches
10 conflicts
0x3f152ba8…cea6
0x34b655…2a6f
10 touches
10 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
10 touches
10 conflicts
0x45885570…ed97
0x34b655…2a6f
10 touches
10 conflicts
0x65bd465d…9770
0x34b655…2a6f
10 touches
10 conflicts
0x839c0c71…bada
0x34b655…2a6f
10 touches
10 conflicts
0x94dabb65…43a3
0x34b655…2a6f
10 touches
10 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
10 conflicts on slot 0x1e9a3afdd5…2da6e5
Audit this contract →
← previous block·next block →recent activity