← previous blocknext block →recent activity
Analyzing
Block #105,844,643
21 transactions · 19 stateful · 2026-09-18 08:34:05 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,844,643 · 21 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
1w02w13w26w013w315w116w017w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x289ac5ba…93c8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x342dbb0b…1b19
0x34b655…2a6f
8 touches
6 conflicts
0xdfce7dfe…5053
0x34b655…2a6f
8 touches
6 conflicts
0x6c7c1a4b…5751
0x34b655…2a6f
6 touches
3 conflicts
0x129babc9…84c6
0x34b655…2a6f
6 touches
3 conflicts
0x2aa7be4c…0f84
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
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
6 conflicts on slot 0x289ac5ba2f…f393c8
Audit this contract →
← previous block·next block →recent activity