← previous blocknext block →recent activity
Analyzing
Block #96,612,998
7 transactions · 7 stateful · 2026-08-16 22:48:15 UTC
Parallelism
43/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,612,998 · 7 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76d36fa4…aaf6
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x93f1d5e2…9290
0x34b655…2a6f
4 touches
1 conflict
0xa8c5904c…e1a7
0x34b655…2a6f
4 touches
1 conflict
0x42c0a5d3…a476
0x34b655…2a6f
4 touches
1 conflict
0x0431e51f…6f91
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
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
6 conflicts on slot 0x76d36fa4cb…8faaf6
Audit this contract →
← previous block·next block →recent activity