← previous blocknext block →recent activity
Analyzing
Block #112,485,278
29 transactions · 24 stateful · 2026-10-11 13:52:11 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,485,278 · 29 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
1w02w13w08w110w115w016w118w019w120w222w023w124w125w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57e5abc1…286f
0x34b655…2a6f
6 touches
3 conflicts
0x9c42dab3…4794
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x6235638c…643a
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x3cf50d44…961b
0x34b655…2a6f
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 0x57e5abc14c…cb286f
Audit this contract →
← previous block·next block →recent activity