← previous blocknext block →recent activity
Analyzing
Block #85,140,503
16 transactions · 15 stateful · 2026-07-02 15:38:17 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,140,503 · 16 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
4w05w16w27w010w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3fde350e…8d43
0x34b655…2a6f
6 touches
3 conflicts
0x1d521b7f…b009
0x34b655…2a6f
4 touches
1 conflict
0x355cda6e…eef8
0x34b655…2a6f
4 touches
1 conflict
0x3e0c8fff…34c8
0x34b655…2a6f
4 touches
1 conflict
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0xa1144aa9…7f67
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc83310b1…c778
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 0x3fde350e54…eb8d43
Audit this contract →
← previous block·next block →recent activity