← previous blocknext block →recent activity
Analyzing
Block #112,081,819
17 transactions · 14 stateful · 2026-10-10 04:02:22 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,081,819 · 17 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
6w07w08w19w010w111w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x198ff0c2…43dc
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xf0343717…908f
0xe52b14…7230
3 touches
1 conflict
0x48a0f121…953b
0x34b655…2a6f
2 touches
0 conflicts
0x636c1534…885d
0x34b655…2a6f
2 touches
0 conflicts
0x7135290c…ee16
0x34b655…2a6f
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 0x51fc8795c8…571266
Audit this contract →
← previous block·next block →recent activity