← previous blocknext block →recent activity
Analyzing
Block #85,253,945
10 transactions · 10 stateful · 2026-07-03 04:13:53 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,253,945 · 10 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
1w02w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x056ec16c…55b9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x2342346a…fe63
0x40c49f…2af0
2 touches
0 conflicts
0x5e98011a…e46f
0x40c49f…2af0
2 touches
0 conflicts
0x9ddbdd4a…1a59
0x40c49f…2af0
2 touches
0 conflicts
0xfd0672f3…ff80
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: Perpl
1 conflict on slot 0x056ec16cdb…0155b9
Audit this contract →
← previous block·next block →recent activity