← previous blocknext block →recent activity
Analyzing
Block #85,918,422
22 transactions · 18 stateful · 2026-07-06 06:00:04 UTC
Parallelism
82/100
Blocked
28%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,918,422 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w18w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb4ece538…a75c
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xbd599972…4906
0xa6afd3…d132
3 touches
1 conflict
0x82df8fa9…0062
0xa6afd3…d132
3 touches
1 conflict
0x8cf3d245…1d0d
0x69df8a…6292
2 touches
0 conflicts
0x915c095e…c1e5
0x69df8a…6292
2 touches
0 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: 0xe52b1424…bb7230
6 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity