← previous blocknext block →recent activity
Analyzing
Block #96,027,564
36 transactions · 33 stateful · 2026-08-14 21:43:22 UTC
Parallelism
64/100
Blocked
67%
Avg conflicts / tx
2.67
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #96,027,564 · 36 txs across 13 waves · depth 13
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
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w07w18w29w210w311w312w413w514w615w716w820w921w1029w234w1135w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
18 touches
36 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
16 touches
28 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x11ba6ecb…5b99
0x34b655…2a6f
8 touches
6 conflicts
0x3ca9a061…1f41
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
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
36 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity