← previous blocknext block →recent activity
Analyzing
Block #93,932,468
18 transactions · 17 stateful · 2026-08-07 13:32:09 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,932,468 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w17w18w210w312w114w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41377979…0a18
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x49d26a9d…432b
0x34b655…2a6f
4 touches
1 conflict
0x6d9ac479…9276
0x34b655…2a6f
4 touches
1 conflict
0x7c1d804e…835c
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 0x413779793d…8f0a18
Audit this contract →
← previous block·next block →recent activity