← previous blocknext block →recent activity
Analyzing
Block #94,759,783
14 transactions · 12 stateful · 2026-08-10 11:10:42 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,759,783 · 14 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
1w09w010w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8e8029d9…ee34
0x065c9d…c394
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x28a16a54…b067
0x065c9d…c394
3 touches
1 conflict
0x744a4b1b…3963
0x065c9d…c394
3 touches
1 conflict
0xba5743c7…21c1
0x1b6862…e19c
2 touches
0 conflicts
0xcba3e575…ba89
0x065c9d…c394
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 0xa7013be2a1…9ac0a8
Audit this contract →
← previous block·next block →recent activity