← previous blocknext block →recent activity
Analyzing
Block #117,205,674
30 transactions · 26 stateful · 2026-10-28 02:21:10 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #117,205,674 · 30 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
1w03w05w06w18w09w110w011w112w216w121w122w223w324w427w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd808de1…5c3c
0x34b655…2a6f
6 touches
3 conflicts
0x885efce3…7496
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x25b1c19a…6d24
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c5
0x508254…98bd
4 touches
1 conflict
0xdb5956e9…9905
0x508254…98bd
4 touches
1 conflict
0xe1c4d8e8…ffa8
0x508254…98bd
4 touches
1 conflict
0x5cefc984…4e80
0xed3727…f3af
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 0xfd808de135…295c3c
Audit this contract →
← previous block·next block →recent activity