← previous blocknext block →recent activity
Analyzing
Block #96,092,902
20 transactions · 19 stateful · 2026-08-15 03:12:01 UTC
Parallelism
90/100
Blocked
5%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,092,902 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x177d036a…1c5d
0x34b655…2a6f
4 touches
1 conflict
0x09396f14…669f
0x34b655…2a6f
4 touches
1 conflict
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x1683d146…5ec2
0x34b655…2a6f
2 touches
0 conflicts
0x1e1f8d85…2092
0x34b655…2a6f
2 touches
0 conflicts
0x29c1a140…099f
0x34b655…2a6f
2 touches
0 conflicts
0x3df0422c…fd38
0x34b655…2a6f
2 touches
0 conflicts
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 0x177d036a8b…531c5d
Audit this contract →
← previous block·next block →recent activity