← previous blocknext block →recent activity
Analyzing
Block #85,744,796
15 transactions · 13 stateful · 2026-07-05 10:43:45 UTC
Parallelism
87/100
Blocked
31%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,744,796 · 15 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
1w02w17w08w09w010w112w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0x56a919c4…ab49
0xad96c3…8d7c
4 touches
1 conflict
0xed59b1cd…8509
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x819e10da…81ce
0xd32edf…ff58
3 touches
1 conflict
0x4dd1db39…a994
0x188d58…ea8e
2 touches
0 conflicts
0x4dd1db39…a996
0x188d58…ea8e
2 touches
0 conflicts
0xc16b7495…25b6
0x188d58…ea8e
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: Perpl
1 conflict on slot 0x57330c5dcf…549973
Audit this contract →
← previous block·next block →recent activity