← previous blocknext block →recent activity
Analyzing
Block #106,959,198
22 transactions · 21 stateful · 2026-09-22 06:05:42 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,959,198 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w18w29w310w414w515w616w017w119w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8c669b4…ea78
0x34b655…2a6f
14 touches
21 conflicts
0x7462b8f2…6312
0x34b655…2a6f
10 touches
10 conflicts
0x5fad6fee…7714
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x6ae47f75…7b45
0x34b655…2a6f
4 touches
1 conflict
0x6c26d635…1bbf
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
21 conflicts on slot 0xf8c669b469…90ea78
Audit this contract →
← previous block·next block →recent activity