← previous blocknext block →recent activity
Analyzing
Block #105,929,028
24 transactions · 21 stateful · 2026-09-18 15:39:42 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,929,028 · 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
6w07w110w011w113w014w115w216w317w422w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x432e26d6…4a16
0x6f6493…b480
10 touches
10 conflicts
0x45d84e6c…8dc2
0x6f6493…b480
10 touches
10 conflicts
0x03c8cf61…0141
0x6f6493…b480
10 touches
10 conflicts
0x5cd0bbc9…222e
0x6f6493…b480
10 touches
10 conflicts
0x5cd0bbc9…2232
0x6f6493…b480
10 touches
10 conflicts
0x7e9a0beb…0882
0x6f6493…b480
10 touches
10 conflicts
0xaebe422d…d34a
0x6f6493…b480
10 touches
10 conflicts
0xc723a01c…5d33
0x6f6493…b480
10 touches
10 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
10 conflicts on slot 0x432e26d6fc…a34a16
Audit this contract →
← previous block·next block →recent activity