← previous blocknext block →recent activity
Analyzing
Block #106,038,407
10 transactions · 10 stateful · 2026-09-19 00:50:21 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,038,407 · 10 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
5w08w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ee73aa5…0d70
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
2 touches
0 conflicts
0x1d5caa5b…df45
0x34b655…2a6f
2 touches
0 conflicts
0x2e72b3d4…73a9
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 0x9ee73aa569…a00d70
Audit this contract →
← previous block·next block →recent activity