← previous blocknext block →recent activity
Analyzing
Block #105,435,113
20 transactions · 20 stateful · 2026-09-16 22:11:30 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,435,113 · 20 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
4w05w110w011w112w213w314w415w516w017w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02ce8c0a…5a96
0x6f6493…b480
12 touches
15 conflicts
0x05864f93…d567
0x6f6493…b480
12 touches
15 conflicts
0x05c7ece7…7836
0x6f6493…b480
12 touches
15 conflicts
0x334105b5…ad57
0x6f6493…b480
12 touches
15 conflicts
0x378d518a…b14e
0x6f6493…b480
12 touches
15 conflicts
0x4c6d653d…3fb1
0x6f6493…b480
12 touches
15 conflicts
0x4f9359e2…cb02
0x6f6493…b480
12 touches
15 conflicts
0x508d3b64…5a24
0x6f6493…b480
12 touches
15 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
15 conflicts on slot 0x02ce8c0aa8…ea5a96
Audit this contract →
← previous block·next block →recent activity