← previous blocknext block →recent activity
Analyzing
Block #86,315,602
16 transactions · 15 stateful · 2026-07-08 02:11:36 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,315,602 · 16 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
2w03w04w05w17w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bdd71a2…b6eb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x2bdbba1d…e867
0x065c9d…c394
2 touches
0 conflicts
0x5e63fd7a…73b3
0x065c9d…c394
2 touches
0 conflicts
0x8b8eaf75…e05d
0x065c9d…c394
2 touches
0 conflicts
0xcee5806c…d92c
0x065c9d…c394
2 touches
0 conflicts
0xda6cbef7…a049
0x065c9d…c394
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 0x3bdd71a21a…eeb6eb
Audit this contract →
← previous block·next block →recent activity