← previous blocknext block →recent activity
Analyzing
Block #106,935,137
30 transactions · 27 stateful · 2026-09-22 04:04:35 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.83
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,935,137 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w08w09w110w211w312w415w118w219w520w621w722w825w128w329w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5cd7d62…6b20
0x34b655…2a6f
16 touches
28 conflicts
0xf1bbd371…e541
0x34b655…2a6f
14 touches
21 conflicts
0x469dac8d…3411
0x34b655…2a6f
10 touches
10 conflicts
0xab981df1…2941
0x34b655…2a6f
10 touches
10 conflicts
0x839c0c71…bada
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x2d84ae4b…161b
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xc5cd7d620e…d86b20
Audit this contract →
← previous block·next block →recent activity