← previous blocknext block →recent activity
Analyzing
Block #106,921,903
24 transactions · 23 stateful · 2026-09-22 02:57:59 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,921,903 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w07w18w09w110w211w312w413w214w215w516w617w718w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x524f0872…0d12
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xa06430bf…57ce
0x34b655…2a6f
10 touches
10 conflicts
0x51087f5a…61f7
0x34b655…2a6f
10 touches
10 conflicts
0x9f46242e…f550
0x34b655…2a6f
8 touches
6 conflicts
0x59b1a0b3…75ba
0x34b655…2a6f
8 touches
6 conflicts
0x7cac1474…e8ec
0x34b655…2a6f
8 touches
6 conflicts
0x853d9e12…128f
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
15 conflicts on slot 0x524f087203…e70d12
Audit this contract →
← previous block·next block →recent activity