← previous blocknext block →recent activity
Analyzing
Block #96,698,244
16 transactions · 14 stateful · 2026-08-17 05:56:59 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,698,244 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w28w39w410w511w613w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x943b8531…5cd6
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x5fde4971…aac9
0x34b655…2a6f
4 touches
1 conflict
0x6f4e7625…aba5
0x34b655…2a6f
4 touches
1 conflict
0x991e2e20…94a6
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
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
21 conflicts on slot 0x943b85313d…215cd6
Audit this contract →
← previous block·next block →recent activity