← previous blocknext block →recent activity
Analyzing
Block #105,844,377
20 transactions · 19 stateful · 2026-09-18 08:32:45 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,844,377 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w28w09w110w211w312w013w114w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e066d6d…36d2
0x6f6493…b480
8 touches
6 conflicts
0x140c08a5…272c
0x6f6493…b480
8 touches
6 conflicts
0x14d28d60…d817
0x6f6493…b480
8 touches
6 conflicts
0x1a54470e…86fe
0x6f6493…b480
8 touches
6 conflicts
0x1b379aee…0077
0x6f6493…b480
8 touches
6 conflicts
0x29afdb22…b774
0x6f6493…b480
8 touches
6 conflicts
0x2ab02e71…9e5d
0x6f6493…b480
8 touches
6 conflicts
0x2c4e2866…ec78
0x6f6493…b480
8 touches
6 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: 0x6f6493e3…08b480
6 conflicts on slot 0x0e066d6d95…8536d2
Audit this contract →
← previous block·next block →recent activity