← previous blocknext block →recent activity
Analyzing
Block #94,717,265
15 transactions · 14 stateful · 2026-08-10 07:35:22 UTC
Parallelism
60/100
Blocked
57%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,717,265 · 15 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
1w03w04w05w16w17w08w19w210w112w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52c1e9be…20ee
0x34b655…2a6f
6 touches
3 conflicts
0xa3f6f7c8…2436
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x0edac7bb…1625
0x34b655…2a6f
6 touches
3 conflicts
0x41377979…0a18
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9a8af3c2…e4ae
0x34b655…2a6f
4 touches
1 conflict
0x9cf9008a…d826
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x52c1e9bea9…4420ee
Audit this contract →
← previous block·next block →recent activity