← previous blocknext block →recent activity
Analyzing
Block #85,915,344
15 transactions · 12 stateful · 2026-07-06 05:39:36 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,915,344 · 15 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
2w03w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0xfe708efe…df34
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x24b878bb…874c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d7057a9…1c18
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 0xe4af4c87c3…c59964
Audit this contract →
← previous block·next block →recent activity