← previous blocknext block →recent activity
Analyzing
Block #85,180,129
16 transactions · 14 stateful · 2026-07-02 20:02:07 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,180,129 · 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
1w02w13w26w07w18w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa164d951…1534
0xe1c8b7…3022
6 touches
3 conflicts
0x67d846dd…358c
0x53bc12…7777
6 touches
3 conflicts
0xbf6b0334…9b9f
0x53bc12…7777
6 touches
3 conflicts
0xcfee13cc…8246
0x53bc12…7777
6 touches
3 conflicts
0x7cf5136f…ba69
0x9f3832…4ae4
6 touches
3 conflicts
0xc6874efb…7efd
0x9f3832…4ae4
6 touches
3 conflicts
0xe502b892…2b46
0x9f3832…4ae4
6 touches
3 conflicts
0xe502b892…2b47
0x9f3832…4ae4
6 touches
3 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: 0xe1c8b733…e33022
3 conflicts on slot 0xa164d95170…fa1534
Audit this contract →
← previous block·next block →recent activity