← previous blocknext block →recent activity
Analyzing
Block #85,225,455
16 transactions · 14 stateful · 2026-07-03 01:04:00 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,225,455 · 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
1w02w14w05w17w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fde64da…aa3e
0x2a68ba…90c5
4 touches
1 conflict
0x95847041…2d63
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7212
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfdfd4993…faf1
0x34b655…2a6f
4 touches
1 conflict
0x9026ca95…db70
0x851145…3f07
3 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
2 touches
0 conflicts
0x56a919c4…ab49
0x01bff4…1071
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: Kuru Exchange: MarginAccount
1 conflict on slot 0x0fde64da0b…a5aa3e
Audit this contract →
← previous block·next block →recent activity