← previous blocknext block →recent activity
Analyzing
Block #86,300,195
20 transactions · 16 stateful · 2026-07-08 00:28:36 UTC
Parallelism
80/100
Blocked
19%
Avg conflicts / tx
0.15
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,300,195 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa8c04ae6…4280
0x34b655…2a6f
3 touches
1 conflict
0xda8d6085…7b09
0x34b655…2a6f
3 touches
1 conflict
0x00000000…0018
0x14b1df…c89b
2 touches
0 conflicts
0x00000000…002f
0x14b1df…c89b
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity