← previous blocknext block →recent activity
Analyzing
Block #106,408,526
21 transactions · 20 stateful · 2026-09-20 07:53:05 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,408,526 · 21 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
1w02w03w04w15w07w110w112w213w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0xf96d61f8…8fd8
0x754704…b603
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x0705cc6c…2c40
0x851145…3f07
4 touches
1 conflict
0x14636d9e…78ad
0x99c7a7…8bf0
4 touches
1 conflict
0x2a46edb5…b5bd
0x99c7a7…8bf0
4 touches
1 conflict
0x37df7523…ccbb
0x754704…b603
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