← previous blocknext block →recent activity
Analyzing
Block #85,408,166
16 transactions · 11 stateful · 2026-07-03 21:21:00 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,408,166 · 16 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
1w010w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
0xb4f750b9…867f
0x34b655…2a6f
4 touches
1 conflict
0xd1a8b9bd…6f8c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfcf55972…5366
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2267f8c4…a571
0x34b655…2a6f
4 touches
1 conflict
0x8c84e7fe…afbd
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 0x9ae859dbf8…e82d84
Audit this contract →
← previous block·next block →recent activity