← previous blocknext block →recent activity
Analyzing
Block #112,610,585
14 transactions · 12 stateful · 2026-10-12 00:22:39 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,610,585 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w010w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0dcc3c4…9d25
0x34b655…2a6f
4 touches
1 conflict
0xb4d77433…e367
0x34b655…2a6f
4 touches
1 conflict
0x65195b39…c610
0x34b655…2a6f
4 touches
1 conflict
0x0d26e7fe…2d7b
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
2 touches
0 conflicts
0x6235638c…643d
0x1b6862…e19c
2 touches
0 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
2 touches
0 conflicts
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
1 conflict on slot 0xb0dcc3c48a…c19d25
Audit this contract →
← previous block·next block →recent activity