← previous blocknext block →recent activity
Analyzing
Block #112,610,744
23 transactions · 19 stateful · 2026-10-12 00:23:27 UTC
Parallelism
91/100
Blocked
16%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,610,744 · 23 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
6w07w114w018w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb473d944…85a5
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xac32f75b…5647
0x34b655…2a6f
4 touches
1 conflict
0x2635f613…40c4
0x34b655…2a6f
2 touches
0 conflicts
0x2ac4cf3c…ec38
0x34b655…2a6f
2 touches
0 conflicts
0x3b2f8bea…8c1f
0x34b655…2a6f
2 touches
0 conflicts
0x4920c316…82e1
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 0xb473d94457…9485a5
Audit this contract →
← previous block·next block →recent activity