← previous blocknext block →recent activity
Analyzing
Block #112,487,397
31 transactions · 30 stateful · 2026-10-11 14:02:51 UTC
Parallelism
94/100
Blocked
10%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,487,397 · 31 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
4w05w116w017w118w024w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2fe6ed6…f8be
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
2 touches
0 conflicts
0xbbca528a…1b10
0x34ae4d…3fc5
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0xd75f2dcb…68f5
0x40c49f…2af0
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 0xc2fe6ed6dd…72f8be
Audit this contract →
← previous block·next block →recent activity