← previous blocknext block →recent activity
Analyzing
Block #96,654,137
10 transactions · 9 stateful · 2026-08-17 02:15:09 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,654,137 · 10 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
1w02w03w14w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcfc2ae3…972b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x8d175439…fb79
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x347e7e76…914b
0x34b655…2a6f
2 touches
0 conflicts
0x34e55350…1320
0x34b655…2a6f
2 touches
0 conflicts
0x362894e6…669f
0x34b655…2a6f
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 0xfcfc2ae3f6…f3972b
Audit this contract →
← previous block·next block →recent activity