← previous blocknext block →recent activity
Analyzing
Block #86,240,193
20 transactions · 15 stateful · 2026-07-07 17:48:02 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,240,193 · 20 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
1w04w05w16w17w28w39w010w114w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x47d4745e…02bb
0x336ed4…c59c
4 touches
1 conflict
0x93c58e4d…9b32
0x336ed4…c59c
4 touches
1 conflict
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x1870f0ac…30d1
0x34b655…2a6f
4 touches
1 conflict
0x1af777a9…b403
0x34b655…2a6f
4 touches
1 conflict
0x1ba42d8c…97a8
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity