← previous blocknext block →recent activity
Analyzing
Block #112,336,308
8 transactions · 8 stateful · 2026-10-11 01:22:42 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,336,308 · 8 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ddc3e4c…bd7c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x1fb37a…a010
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x02b40964…6885
0x34b655…2a6f
2 touches
0 conflicts
0x0984693a…9608
0x34b655…2a6f
2 touches
0 conflicts
0x1b5989b4…4dbf
0x34b655…2a6f
2 touches
0 conflicts
0x35eab2e5…3c0a
0x34b655…2a6f
2 touches
0 conflicts
0x38572699…db2d
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 0x2ddc3e4c8c…d8bd7c
Audit this contract →
← previous block·next block →recent activity