← previous blocknext block →recent activity
Analyzing
Block #86,786,391
30 transactions · 25 stateful · 2026-07-10 06:39:47 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,786,391 · 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
1w02w03w16w08w19w012w013w114w215w316w417w418w222w323w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xec7fe04a…3c56
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
6 touches
3 conflicts
0x10970e1d…90df
0x34b655…2a6f
6 touches
3 conflicts
0x49a97bff…33ed
0x34b655…2a6f
4 touches
1 conflict
0x4c43bbae…1403
0x34b655…2a6f
4 touches
1 conflict
0x59c0d3d2…2e18
0x34b655…2a6f
4 touches
1 conflict
0x74550a4b…68bd
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity