← previous blocknext block →recent activity
Analyzing
Block #86,054,433
20 transactions · 16 stateful · 2026-07-06 21:08:10 UTC
Parallelism
90/100
Blocked
13%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,054,433 · 20 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
2w03w04w05w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37d710c8…45c1
0x34b655…2a6f
4 touches
1 conflict
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe8452acc…bd17
0x065c9d…c394
3 touches
1 conflict
0x3f0844d9…f2cb
0x065c9d…c394
3 touches
1 conflict
0xcc27e7c0…14b7
0x065c9d…c394
3 touches
1 conflict
0xc2e13187…104d
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
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 0x37d710c811…2145c1
Audit this contract →
← previous block·next block →recent activity