← previous blocknext block →recent activity
Analyzing
Block #86,238,217
24 transactions · 21 stateful · 2026-07-07 17:34:50 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,238,217 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w07w08w19w210w311w417w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0x47d4745e…02bb
0x336ed4…c59c
8 touches
6 conflicts
0x00000000…000a
0x90c374…be45
8 touches
6 conflicts
0x34443913…cbf3
0x336ed4…c59c
8 touches
6 conflicts
0x00000000…000b
0x90c374…be45
8 touches
6 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
6 touches
3 conflicts
0x4a870d86…79ef
0x336ed4…c59c
6 touches
3 conflicts
0x2eb48eb7…9d68
0x8d1565…6723
6 touches
3 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: 0x04fdeac2…f747d7
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity