← previous blocknext block →recent activity
Analyzing
Block #86,484,827
20 transactions · 20 stateful · 2026-07-08 21:02:31 UTC
Parallelism
70/100
Blocked
45%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,484,827 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w28w313w314w216w217w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc948dbdc…199a
0x34b655…2a6f
12 touches
15 conflicts
0x65e795ca…0320
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x01c969a3…227b
0x34b655…2a6f
4 touches
1 conflict
0x0d55d89d…a4ec
0x34b655…2a6f
4 touches
1 conflict
0x21d22421…0b7a
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
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
15 conflicts on slot 0xc948dbdcb8…f4199a
Audit this contract →
← previous block·next block →recent activity