← previous blocknext block →recent activity
Analyzing
Block #106,946,577
28 transactions · 14 stateful · 2026-09-22 05:02:10 UTC
Parallelism
93/100
Blocked
14%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,946,577 · 28 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w110w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46483cb1…e7ca
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x37eb66f0…f797
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x8e80434a…a96d
0x0555e3…2b9c
2 touches
0 conflicts
0xa46da752…01ff
0x0555e3…2b9c
2 touches
0 conflicts
0x11ab41cc…060f
0x065c9d…c394
2 touches
0 conflicts
0x95523e2a…4c01
0x065c9d…c394
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
1 conflict on slot 0x46483cb14f…c1e7ca
Audit this contract →
← previous block·next block →recent activity