← previous blocknext block →recent activity
Analyzing
Block #85,919,656
16 transactions · 11 stateful · 2026-07-06 06:08:17 UTC
Parallelism
88/100
Blocked
9%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,919,656 · 16 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
13w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96b47eb9…c3c3
0x34b655…2a6f
4 touches
1 conflict
0xbc04d98e…a484
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x183f6110…e0ee
0x6657d1…8ccc
2 touches
0 conflicts
0x18aeb684…3b2e
0x6657d1…8ccc
2 touches
0 conflicts
0x23e697a1…6193
0x6657d1…8ccc
2 touches
0 conflicts
0x55183c4a…3f2c
0x6657d1…8ccc
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 0x96b47eb9b8…d8c3c3
Audit this contract →
← previous block·next block →recent activity