← previous blocknext block →recent activity
Analyzing
Block #86,300,181
16 transactions · 13 stateful · 2026-07-08 00:28:30 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,300,181 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w29w010w311w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d9867ad…6d9a
0x34b655…2a6f
10 touches
10 conflicts
0x27dd8ebd…6d57
0x34b655…2a6f
8 touches
6 conflicts
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0xfcb5fe79…c20a
0x34b655…2a6f
4 touches
1 conflict
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0xd911522b…e960
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdf25059f…3f2e
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
10 conflicts on slot 0x1d9867ade5…7b6d9a
Audit this contract →
← previous block·next block →recent activity