← previous blocknext block →recent activity
Analyzing
Block #94,668,529
19 transactions · 18 stateful · 2026-08-10 03:30:14 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
1.16
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,668,529 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w010w211w312w413w515w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e52e46…0894
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xbfc5d23d…6ad7
0x34b655…2a6f
6 touches
3 conflicts
0x50da4294…f6ed
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa5811d93…8c73
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0xe2e52e4663…6f0894
Audit this contract →
← previous block·next block →recent activity