← previous blocknext block →recent activity
Analyzing
Block #105,633,824
19 transactions · 19 stateful · 2026-09-17 14:51:37 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,633,824 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w07w210w311w012w113w314w415w516w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x88e92ec7…696d
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
8 touches
6 conflicts
0x4ab195e7…0967
0x34b655…2a6f
8 touches
6 conflicts
0xa253f0ea…08e6
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity