← previous blocknext block →recent activity
Analyzing
Block #86,054,945
30 transactions · 24 stateful · 2026-07-06 21:11:36 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,054,945 · 30 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
2w03w15w210w011w116w218w021w122w224w025w126w227w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x46005a44…f34b
0xa6afd3…d132
6 touches
3 conflicts
0x8876d94c…8435
0x2a68ba…90c5
4 touches
1 conflict
0x156f9d43…a708
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x61377ba1…0bef
0xa6afd3…d132
4 touches
1 conflict
0x7c51d9aa…af39
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity