← previous blocknext block →recent activity
Analyzing
Block #85,514,098
16 transactions · 12 stateful · 2026-07-04 09:06:15 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,514,098 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w110w211w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa20a130c…5d59
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x13af9e48…d72a
0x34b655…2a6f
6 touches
3 conflicts
0x665a59a6…79a6
0x34b655…2a6f
6 touches
3 conflicts
0xed59b1cd…8509
0x34b655…2a6f
6 touches
3 conflicts
0x25117bec…1abf
0x34b655…2a6f
4 touches
1 conflict
0x2697123c…8526
0x34b655…2a6f
4 touches
1 conflict
0x353a3a00…5e0a
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
6 conflicts on slot 0xa20a130ca6…b85d59
Audit this contract →
← previous block·next block →recent activity