← previous blocknext block →recent activity
Analyzing
Block #96,145,778
12 transactions · 12 stateful · 2026-08-15 07:38:02 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,145,778 · 12 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
4w05w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bea6eae…9f7b
0x34b655…2a6f
4 touches
1 conflict
0xa5a8ffca…8de2
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xe3c082c7…f032
0x34b655…2a6f
4 touches
1 conflict
0x81f0d62d…5982
0x065c9d…c394
2 touches
0 conflicts
0x9ff176a9…152e
0x065c9d…c394
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 0x2bea6eae34…b89f7b
Audit this contract →
← previous block·next block →recent activity