← previous blocknext block →recent activity
Analyzing
Block #106,959,465
30 transactions · 21 stateful · 2026-09-22 06:07:03 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,959,465 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w27w010w312w113w221w324w428w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0xc5f336ca…912e
0x34b655…2a6f
6 touches
3 conflicts
0xdfb496de…8129
0x34b655…2a6f
5 touches
3 conflicts
0x8b501dcf…1040
0x34b655…2a6f
4 touches
1 conflict
0xacd9c381…91d1
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity