← previous blocknext block →recent activity
Analyzing
Block #85,840,347
21 transactions · 18 stateful · 2026-07-05 21:19:58 UTC
Parallelism
81/100
Blocked
28%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,840,347 · 21 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
4w05w16w27w310w011w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8b4ef1bd…ee1a
0x065c9d…c394
2 touches
0 conflicts
0x97a0cd85…cfca
0x080ec9…fe74
2 touches
0 conflicts
0xa0bab64e…b8c0
0x080ec9…fe74
2 touches
0 conflicts
0x00000000…0008
0x14c8e4…fdcb
2 touches
0 conflicts
0x00000000…0009
0x14c8e4…fdcb
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: 0x04fdeac2…f747d7
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity