← previous blocknext block →recent activity
Analyzing
Block #106,916,799
17 transactions · 12 stateful · 2026-09-22 02:32:17 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,916,799 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w110w211w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5800c316…0e19
0x34b655…2a6f
8 touches
6 conflicts
0x7fc8f46e…0f75
0x34b655…2a6f
8 touches
6 conflicts
0x524f0872…0d12
0x34b655…2a6f
6 touches
3 conflicts
0x57bf1a1b…914e
0x34b655…2a6f
4 touches
1 conflict
0x85bfd0af…ce96
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x626418b6…20b6
0x3bd359…433a
2 touches
0 conflicts
0x690117b9…2820
0x3bd359…433a
2 touches
0 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
6 conflicts on slot 0x5800c316d7…770e19
Audit this contract →
← previous block·next block →recent activity