← previous blocknext block →recent activity
Analyzing
Block #85,678,549
8 transactions · 7 stateful · 2026-07-05 03:21:12 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,678,549 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86a11e8a…07f7
0x34b655…2a6f
4 touches
1 conflict
0x889487c1…06c6
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x5713acd4…bdb7
0x34b655…2a6f
3 touches
1 conflict
0x200db05e…6327
0x34b655…2a6f
2 touches
0 conflicts
0x22d3c767…e4d1
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 0x86a11e8a34…a207f7
Audit this contract →
← previous block·next block →recent activity