← previous blocknext block →recent activity
Analyzing
Block #85,140,861
13 transactions · 13 stateful · 2026-07-02 15:40:40 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,140,861 · 13 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
1w03w04w16w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35eed8dc…c0c3
0x34b655…2a6f
4 touches
1 conflict
0x4063c153…d0cb
0x34b655…2a6f
4 touches
1 conflict
0x4c5679e7…8b33
0x34b655…2a6f
4 touches
1 conflict
0x540d726f…481d
0x34b655…2a6f
4 touches
1 conflict
0x587911c7…9e01
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0x7c17afbb…220f
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
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
1 conflict on slot 0x35eed8dc67…e0c0c3
Audit this contract →
← previous block·next block →recent activity