← previous blocknext block →recent activity
Analyzing
Block #106,053,972
16 transactions · 16 stateful · 2026-09-19 02:08:41 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,053,972 · 16 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
1w04w05w18w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x10683d5f…4f0c
0x6f6493…b480
4 touches
1 conflict
0x16ac6f02…10e6
0x6f6493…b480
4 touches
1 conflict
0x174aad88…9743
0x6f6493…b480
4 touches
1 conflict
0x17759ebc…d4f9
0x6f6493…b480
4 touches
1 conflict
0x1a151dca…c604
0x6f6493…b480
4 touches
1 conflict
0x1a151dca…c608
0x6f6493…b480
4 touches
1 conflict
0x3485d0b8…7523
0x6f6493…b480
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity