← previous blocknext block →recent activity
Analyzing
Block #94,751,302
43 transactions · 32 stateful · 2026-08-10 10:27:47 UTC
Parallelism
88/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,751,302 · 43 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w09w113w214w318w020w022w023w125w227w328w130w431w235w336w340w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2db666e7…b931
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xeae24c…0be0
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
6 touches
3 conflicts
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x45911da6…5523
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
10 conflicts on slot 0x2db666e705…a0b931
Audit this contract →
← previous block·next block →recent activity