← previous blocknext block →recent activity
Analyzing
Block #117,293,988
34 transactions · 24 stateful · 2026-10-28 09:45:56 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #117,293,988 · 34 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
1w03w17w08w09w110w212w313w117w118w021w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2575a0e…f92b
0xc9de99…405d
8 touches
6 conflicts
0xc2575a0e…f805
0xc9de99…405d
6 touches
3 conflicts
0xab07df27…2647
0x264123…670e
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x5ee3f950…32bf
0x264123…670e
4 touches
1 conflict
0xebc2e0d7…958e
0x3bd359…433a
4 touches
1 conflict
0x06771d0e…6cf3
0x508254…98bd
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: 0xc9de998e…86405d
6 conflicts on slot 0xc2575a0e9e…71f92b
Audit this contract →
← previous block·next block →recent activity