← previous blocknext block →recent activity
Analyzing
Block #106,198,854
32 transactions · 31 stateful · 2026-09-19 14:17:49 UTC
Parallelism
81/100
Blocked
16%
Avg conflicts / tx
0.31
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,198,854 · 32 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
2w03w17w016w226w328w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfccf4b5b…66ca
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x07610b8e…6093
0x34b655…2a6f
4 touches
1 conflict
0x69889858…829f
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 0xfccf4b5b29…a966ca
Audit this contract →
← previous block·next block →recent activity