← previous blocknext block →recent activity
Analyzing
Block #96,488,359
11 transactions · 9 stateful · 2026-08-16 12:21:03 UTC
Parallelism
73/100
Blocked
56%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,488,359 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w16w07w18w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefb805bc…0d8d
0x34b655…2a6f
4 touches
1 conflict
0xc1f6acda…6abb
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe61d2149…e827
0x34b655…2a6f
4 touches
1 conflict
0x09396f14…669f
0x34b655…2a6f
4 touches
1 conflict
0x0e8d7d5d…4a97
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4376
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4377
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
1 conflict on slot 0xefb805bca9…d20d8d
Audit this contract →
← previous block·next block →recent activity