← previous blocknext block →recent activity
Analyzing
Block #106,373,100
16 transactions · 14 stateful · 2026-09-20 04:54:48 UTC
Parallelism
81/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,373,100 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w011w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x94c52ce6…4834
0x065c9d…c394
3 touches
1 conflict
0x3576f12a…66f2
0x065c9d…c394
3 touches
1 conflict
0x08c5d8d8…c7c1
0x34b655…2a6f
2 touches
0 conflicts
0x10180d79…9dad
0x34b655…2a6f
2 touches
0 conflicts
0x102ab3ca…83b4
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity