← previous blocknext block →recent activity
Analyzing
Block #106,028,879
22 transactions · 20 stateful · 2026-09-19 00:02:24 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,028,879 · 22 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
1w02w13w012w114w116w218w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x024b482b…16b0
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1269
0x34b655…2a6f
4 touches
1 conflict
0x7dd96c96…7335
0x34b655…2a6f
4 touches
1 conflict
0x839d77a9…9a51
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity