← previous blocknext block →recent activity
Analyzing
Block #94,718,590
35 transactions · 30 stateful · 2026-08-10 07:42:02 UTC
Parallelism
89/100
Blocked
50%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,718,590 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w08w19w311w114w215w016w117w018w121w022w125w126w227w232w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a51d6fa…1ea1
0x34b655…2a6f
6 touches
3 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
6 touches
3 conflicts
0x9a555477…19a8
0x754704…b603
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb33ff823…1188
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0002
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
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
3 conflicts on slot 0x0a51d6fab7…371ea1
Audit this contract →
← previous block·next block →recent activity