← previous blocknext block →recent activity
Analyzing
Block #90,395,754
11 transactions · 10 stateful · 2026-07-26 04:51:59 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,395,754 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w29w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61d37f4f…61d2
0x34b655…2a6f
6 touches
3 conflicts
0x112eb509…62f7
0x34b655…2a6f
4 touches
1 conflict
0x376c9634…97d2
0x34b655…2a6f
4 touches
1 conflict
0xac8a5059…fd42
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x1bd6ddeb…9a19
0x34b655…2a6f
2 touches
0 conflicts
0x349f436e…80e6
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
3 conflicts on slot 0x61d37f4fd4…e161d2
Audit this contract →
← previous block·next block →recent activity