← previous blocknext block →recent activity
Analyzing
Block #90,371,946
7 transactions · 7 stateful · 2026-07-26 02:49:36 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,371,946 · 7 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
0x1110ff7d…d969
0x34b655…2a6f
4 touches
1 conflict
0x7c09c53e…64b4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xcb4873be…e58e
0x34b655…2a6f
4 touches
1 conflict
0x227238a6…6f47
0x34b655…2a6f
2 touches
0 conflicts
0x3fcb7de0…0bb0
0x34b655…2a6f
2 touches
0 conflicts
0x3fcb7de0…0bb1
0x34b655…2a6f
2 touches
0 conflicts
0x42d5e8f3…5930
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 0x1110ff7de7…c9d969
Audit this contract →
← previous block·next block →recent activity