← previous blocknext block →recent activity
Analyzing
Block #106,216,663
29 transactions · 28 stateful · 2026-09-19 15:47:30 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,216,663 · 29 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
2w03w14w27w016w117w220w121w322w423w524w626w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f5d6958…8ad9
0x34b655…2a6f
14 touches
21 conflicts
0x742436a7…c4d4
0x34b655…2a6f
10 touches
10 conflicts
0x4118bd12…924a
0x34b655…2a6f
10 touches
10 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0x163c8eca…7b49
0x34b655…2a6f
6 touches
3 conflicts
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 0x0f5d695892…188ad9
Audit this contract →
← previous block·next block →recent activity