← previous blocknext block →recent activity
Analyzing
Block #85,161,188
19 transactions · 19 stateful · 2026-07-02 17:56:00 UTC
Parallelism
89/100
Blocked
26%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,161,188 · 19 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
1w02w03w04w15w06w112w113w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea2644f5…8c97
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xffe3c1a4…267a
0x065c9d…c394
4 touches
1 conflict
0xadd60dcf…026f
0x065c9d…c394
3 touches
1 conflict
0xe911404d…c5a6
0x065c9d…c394
3 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 0xea2644f55c…128c97
Audit this contract →
← previous block·next block →recent activity