← previous blocknext block →recent activity
Analyzing
Block #106,282,229
27 transactions · 27 stateful · 2026-09-19 21:17:30 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.67
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,282,229 · 27 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
1w02w08w09w110w112w215w216w317w418w519w622w326w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd426e0d…be2b
0x34b655…2a6f
14 touches
21 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xfac38cc8…fb9d
0x34b655…2a6f
8 touches
6 conflicts
0xe098738f…9bbe
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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 0xfd426e0dbc…97be2b
Audit this contract →
← previous block·next block →recent activity