← previous blocknext block →recent activity
Analyzing
Block #86,084,804
23 transactions · 12 stateful · 2026-07-07 00:30:38 UTC
Parallelism
91/100
Blocked
17%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,084,804 · 23 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
12w014w021w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
0x70005f1b…a377
0x34b655…2a6f
4 touches
1 conflict
0xe75ce681…ba60
0x188d58…ea8e
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
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 0x4ec9ff52ce…67e6f7
Audit this contract →
← previous block·next block →recent activity