← previous blocknext block →recent activity
Analyzing
Block #96,601,436
16 transactions · 13 stateful · 2026-08-16 21:50:05 UTC
Parallelism
63/100
Blocked
46%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,601,436 · 16 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
1w02w14w25w36w010w311w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x690c87ea…f239
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0x427c9fc4…5cee
0x34b655…2a6f
4 touches
1 conflict
0x55807665…9c75
0x34b655…2a6f
4 touches
1 conflict
0x5d0a3cbd…ab19
0x34b655…2a6f
4 touches
1 conflict
0x6c60fbcf…8744
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
15 conflicts on slot 0x690c87eaac…3ff239
Audit this contract →
← previous block·next block →recent activity