← previous blocknext block →recent activity
Analyzing
Block #117,425,820
29 transactions · 26 stateful · 2026-10-28 20:49:28 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #117,425,820 · 29 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
1w02w03w15w18w012w214w215w216w321w027w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x666889a7…968f
0x264123…670e
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x33ef7909…fc8e
0x264123…670e
6 touches
3 conflicts
0xab07df27…2647
0x264123…670e
4 touches
1 conflict
0xe8b6c85c…44e0
0x264123…670e
4 touches
1 conflict
0x73449ddd…cab7
0x34b655…2a6f
4 touches
1 conflict
0x4b458a59…2180
0xc9de99…405d
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
3 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity