← previous blocknext block →recent activity
Analyzing
Block #96,798,172
18 transactions · 15 stateful · 2026-08-17 14:19:35 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,798,172 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w09w110w211w212w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34d4ef1a…0345
0x34b655…2a6f
6 touches
3 conflicts
0xec0bdd60…3223
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2bac71c3…3296
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x81b6effd…f531
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
3 conflicts on slot 0x34d4ef1a26…5e0345
Audit this contract →
← previous block·next block →recent activity