← previous blocknext block →recent activity
Analyzing
Block #90,998,004
15 transactions · 14 stateful · 2026-07-28 07:27:21 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,998,004 · 15 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
1w02w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x5efd583e…c41a
0x34b655…2a6f
4 touches
1 conflict
0xb1c0aa3e…a104
0x065c9d…c394
2 touches
0 conflicts
0xc048608d…c212
0x065c9d…c394
2 touches
0 conflicts
0xf47ed33e…3c1f
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 0x8cd684d0d7…f5c3cb
Audit this contract →
← previous block·next block →recent activity