← previous blocknext block →recent activity
Analyzing
Block #85,146,323
16 transactions · 14 stateful · 2026-07-02 16:17:05 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,146,323 · 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
0xd16df6cd…5532
0x40c49f…2af0
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x975e9149…3a36
0x40c49f…2af0
4 touches
1 conflict
0x5be7bf01…1614
0x40c49f…2af0
3 touches
1 conflict
0x7a09d881…d5a6
0x40c49f…2af0
3 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
2 touches
0 conflicts
0x0e5051a7…6296
0x40c49f…2af0
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: 0x40c49f17…d22af0
1 conflict on slot 0xd16df6cdbe…065532
Audit this contract →
← previous block·next block →recent activity