← previous blocknext block →recent activity
Analyzing
Block #112,486,152
28 transactions · 22 stateful · 2026-10-11 13:56:35 UTC
Parallelism
82/100
Blocked
55%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,486,152 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w08w19w210w311w417w219w020w121w222w323w424w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a663e9a…a9c6
0x508254…98bd
10 touches
10 conflicts
0xfafd7891…e02c
0x508254…98bd
10 touches
10 conflicts
0x00000000…0002
0x125f12…a50b
10 touches
10 conflicts
0x4ea2b33b…7dbc
0x508254…98bd
10 touches
10 conflicts
0x3a663e9a…a9c5
0x508254…98bd
8 touches
6 conflicts
0xb7b446d2…2006
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xfafd7891…e00c
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: 0x508254c8…4a98bd
10 conflicts on slot 0x3a663e9a3a…2fa9c6
Audit this contract →
← previous block·next block →recent activity