← previous blocknext block →recent activity
Analyzing
Block #93,315,574
10 transactions · 9 stateful · 2026-08-05 09:50:22 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,315,574 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d778644…7bb9
0x34b655…2a6f
4 touches
1 conflict
0x3e72a2d1…ce0e
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0xa065ec1a…6e80
0x065c9d…c394
2 touches
0 conflicts
0xd357f6b7…a423
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x1d778644aa…a37bb9
Audit this contract →
← previous block·next block →recent activity