← previous blocknext block →recent activity
Analyzing
Block #112,605,935
16 transactions · 16 stateful · 2026-10-11 23:59:15 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,605,935 · 16 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
5w06w17w08w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe62065a4…c226
0x34b655…2a6f
4 touches
1 conflict
0xb4656137…584f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
2 touches
0 conflicts
0x00000000…0002
0x1fb37a…a010
2 touches
0 conflicts
0x0e17c5aa…88fc
0x34b655…2a6f
2 touches
0 conflicts
0x1b458e47…5ab5
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 0xe62065a40f…1cc226
Audit this contract →
← previous block·next block →recent activity