← previous blocknext block →recent activity
Analyzing
Block #111,829,511
31 transactions · 28 stateful · 2026-10-09 06:52:48 UTC
Parallelism
87/100
Blocked
32%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #111,829,511 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w08w213w116w219w123w124w229w030w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004f
0x80c745…7210
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x1ac086e8…0078
0x0555e3…2b9c
4 touches
1 conflict
0xd8cb7957…55a7
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x5bd10f19…273b
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x65903ef9a0…7d2567
Audit this contract →
← previous block·next block →recent activity