← previous blocknext block →recent activity
Analyzing
Block #85,273,652
19 transactions · 17 stateful · 2026-07-03 06:25:03 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,273,652 · 19 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
1w03w04w15w16w27w310w011w112w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
4 touches
1 conflict
0x93c58e4d…9b32
0x336ed4…c59c
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x10a2bd5d…ad6d
0x8d1565…6723
4 touches
1 conflict
0x00000000…000a
0x90c374…be45
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
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
6 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity