← previous blocknext block →recent activity
Analyzing
Block #86,443,176
14 transactions · 14 stateful · 2026-07-08 16:23:47 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,443,176 · 14 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
1w02w14w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0xd19c9d38…b459
0x34b655…2a6f
4 touches
1 conflict
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0x83a92080…e3da
0x34b655…2a6f
4 touches
1 conflict
0xc621b9f3…f80a
0xd32edf…ff58
3 touches
1 conflict
0x59645a97…3ca1
0x34b655…2a6f
2 touches
0 conflicts
0x6fa9723f…80fd
0x34b655…2a6f
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 0x747f609d18…eb1555
Audit this contract →
← previous block·next block →recent activity