← previous blocknext block →recent activity
Analyzing
Block #112,371,798
22 transactions · 19 stateful · 2026-10-11 04:21:15 UTC
Parallelism
91/100
Blocked
5%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,371,798 · 22 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
6w010w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbefaf45…1618
0x34b655…2a6f
4 touches
1 conflict
0xcdf146be…db81
0x34b655…2a6f
4 touches
1 conflict
0x0008ef72…a804
0x34b655…2a6f
2 touches
0 conflicts
0x0667a366…00ce
0x34b655…2a6f
2 touches
0 conflicts
0x08527e66…b051
0x34b655…2a6f
2 touches
0 conflicts
0x248c4abe…a927
0x34b655…2a6f
2 touches
0 conflicts
0x423ad46a…b3b9
0x34b655…2a6f
2 touches
0 conflicts
0x57d935a0…696f
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 0xbbefaf45da…a61618
Audit this contract →
← previous block·next block →recent activity