← previous blocknext block →recent activity
Analyzing
Block #106,916,087
24 transactions · 22 stateful · 2026-09-22 02:28:42 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,916,087 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w110w211w312w413w014w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0xe6a595bf…3c45
0x34b655…2a6f
10 touches
10 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
10 touches
10 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
10 touches
10 conflicts
0x158cd73a…d47b
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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
10 conflicts on slot 0x42522e76ce…082592
Audit this contract →
← previous block·next block →recent activity