← previous blocknext block →recent activity
Analyzing
Block #86,991,619
19 transactions · 17 stateful · 2026-07-11 05:31:38 UTC
Parallelism
89/100
Blocked
12%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,991,619 · 19 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
1w04w17w08w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd38f4e6…586c
0x34b655…2a6f
4 touches
1 conflict
0xdd38f4e6…586d
0x34b655…2a6f
4 touches
1 conflict
0xe589d762…b275
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x5ce8e9ad…6207
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
1 conflict on slot 0xdd38f4e69f…fd586c
Audit this contract →
← previous block·next block →recent activity