← previous blocknext block →recent activity
Analyzing
Block #116,089,676
28 transactions · 25 stateful · 2026-10-24 04:36:39 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #116,089,676 · 28 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
2w03w14w25w37w09w112w013w117w219w020w121w222w324w326w027w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a663e9a…a9c6
0x508254…98bd
8 touches
6 conflicts
0xba0fd3cf…a6cc
0x34b655…2a6f
8 touches
6 conflicts
0x4ea2b33b…7dbc
0x508254…98bd
8 touches
6 conflicts
0xdb5956e9…9968
0x508254…98bd
8 touches
6 conflicts
0xdb5956e9…9905
0x508254…98bd
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
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: 0x508254c8…4a98bd
6 conflicts on slot 0x3a663e9a3a…2fa9c6
Audit this contract →
← previous block·next block →recent activity