← previous blocknext block →recent activity
Analyzing
Block #106,457,368
13 transactions · 13 stateful · 2026-09-20 11:58:57 UTC
Parallelism
62/100
Blocked
54%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,457,368 · 13 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
1w02w13w14w25w26w07w110w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe283e878…7262
0x34b655…2a6f
6 touches
3 conflicts
0x01ab5050…95b8
0x34b655…2a6f
6 touches
3 conflicts
0xe8fab3e2…3dda
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0x33365a6a…7e0b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
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
3 conflicts on slot 0xe283e878f8…797262
Audit this contract →
← previous block·next block →recent activity