← previous blocknext block →recent activity
Analyzing
Block #86,058,152
16 transactions · 15 stateful · 2026-07-06 21:32:55 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,058,152 · 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
1w02w14w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0x7d6b9af1…9a38
0x34b655…2a6f
4 touches
1 conflict
0x84b98a86…5c11
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x262736d9…798f
0x40c49f…2af0
2 touches
0 conflicts
0x3797e16f…2798
0x40c49f…2af0
2 touches
0 conflicts
0xed4d31b7…c40e
0x40c49f…2af0
2 touches
0 conflicts
0xfc2ab98a…77a5
0x40c49f…2af0
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 0x76ed8777f7…0c1e5f
Audit this contract →
← previous block·next block →recent activity