← previous blocknext block →recent activity
Analyzing
Block #86,809,343
25 transactions · 19 stateful · 2026-07-10 09:13:05 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,809,343 · 25 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
4w05w18w09w010w011w114w015w116w217w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6ed530e…fa7d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
6 touches
3 conflicts
0x1da1c6cb…bb3f
0x34b655…2a6f
4 touches
1 conflict
0x204ccae2…8dc1
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8344e533…436c
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 0xc6ed530ecc…a9fa7d
Audit this contract →
← previous block·next block →recent activity