← previous blocknext block →recent activity
Analyzing
Block #112,577,925
18 transactions · 16 stateful · 2026-10-11 21:38:20 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,577,925 · 18 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
1w02w110w011w112w213w314w315w416w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3fcefd4…c129
0x34b655…2a6f
8 touches
6 conflicts
0x5d0915af…762d
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0057
0x1b6862…e19c
4 touches
1 conflict
0x063eca74…c2e2
0x1b6862…e19c
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
6 conflicts on slot 0xc3fcefd4d3…48c129
Audit this contract →
← previous block·next block →recent activity