← previous blocknext block →recent activity
Analyzing
Block #112,370,420
28 transactions · 27 stateful · 2026-10-11 04:14:19 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,370,420 · 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
2w03w14w05w16w28w09w111w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d328a63…9623
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xf8ba9581…ad55
0x34b655…2a6f
4 touches
1 conflict
0x0b4016b1…306b
0x34b655…2a6f
4 touches
1 conflict
0x0d69b170…f45b
0x34b655…2a6f
4 touches
1 conflict
0x1bd06eeb…d422
0x34b655…2a6f
4 touches
1 conflict
0x27daa6a5…11a4
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
10 conflicts on slot 0x5d328a6386…839623
Audit this contract →
← previous block·next block →recent activity