← previous blocknext block →recent activity
Analyzing
Block #94,485,969
76 transactions · 74 stateful · 2026-08-09 12:12:02 UTC
Parallelism
97/100
Blocked
3%
Avg conflicts / tx
0.03
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,485,969 · 76 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
2w03w14w070w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x007646ce…bc62
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xc740bb93…5486
0x065c9d…c394
3 touches
1 conflict
0x0f15f74f…8d71
0x34b655…2a6f
2 touches
0 conflicts
0x2ad29b13…92e0
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
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: Perpl
1 conflict on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity