← previous blocknext block →recent activity
Analyzing
Block #96,213,193
37 transactions · 31 stateful · 2026-08-15 13:17:05 UTC
Parallelism
68/100
Blocked
74%
Avg conflicts / tx
2.27
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #96,213,193 · 37 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w28w39w411w312w513w614w715w816w917w1026w127w528w1029w231w336w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x53f393fa…00b9
0x34b655…2a6f
12 touches
15 conflicts
0xafb8e71e…9285
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0x424934c8…f2f1
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 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
28 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity