← previous blocknext block →recent activity
Analyzing
Block #86,450,184
14 transactions · 12 stateful · 2026-07-08 17:10:40 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,450,184 · 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
4w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5a1a5cb…5ca1
0x34b655…2a6f
4 touches
1 conflict
0xee4fe1f7…3ead
0x34b655…2a6f
4 touches
1 conflict
0x66cc379b…36fd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdba422af…42ec
0x34b655…2a6f
4 touches
1 conflict
0xdcb14969…a04e
0x34b655…2a6f
4 touches
1 conflict
0x2723fcc7…a6c0
0x40c49f…2af0
2 touches
0 conflicts
0x3c66b1a7…ca53
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 0xe5a1a5cb00…a05ca1
Audit this contract →
← previous block·next block →recent activity