← previous blocknext block →recent activity
Analyzing
Block #84,336,118
21 transactions · 18 stateful · 2026-06-28 22:13:04 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,336,118 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w28w09w114w015w117w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfe06a18…b5b5
0x69df8a…6292
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x3fcc24d4…fa74
0x851145…3f07
6 touches
3 conflicts
0x6b76d7a1…d19b
0x851145…3f07
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x7a12283f…b18a
0x69df8a…6292
6 touches
3 conflicts
0x915c095e…c1e5
0x69df8a…6292
6 touches
3 conflicts
0xd8fd2add…50fc
0x69df8a…6292
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: 0x69df8a43…506292
3 conflicts on slot 0xcfe06a182e…7ab5b5
Audit this contract →
← previous block·next block →recent activity