← previous blocknext block →recent activity
Analyzing
Block #112,355,697
12 transactions · 11 stateful · 2026-10-11 03:00:14 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,355,697 · 12 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
3w05w07w08w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fb58a37…ea7e
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x30c7fdeb…d657
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x01991769…14a9
0x34b655…2a6f
2 touches
0 conflicts
0x0c125c1d…4bf0
0x34b655…2a6f
2 touches
0 conflicts
0x0fcb5a25…9f42
0x34b655…2a6f
2 touches
0 conflicts
0x28771dcc…c580
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 0x1fb58a37c2…83ea7e
Audit this contract →
← previous block·next block →recent activity