← previous blocknext block →recent activity
Analyzing
Block #90,538,831
12 transactions · 12 stateful · 2026-07-26 16:56:55 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,538,831 · 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
2w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e0471c0…f681
0x34b655…2a6f
4 touches
1 conflict
0x1c3295fd…097a
0x34b655…2a6f
4 touches
1 conflict
0x41d39318…d624
0x34b655…2a6f
4 touches
1 conflict
0x48d1f04a…c2b5
0x34b655…2a6f
4 touches
1 conflict
0x4a6982a4…158c
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7743
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7744
0x34b655…2a6f
4 touches
1 conflict
0x78346476…4311
0x34b655…2a6f
4 touches
1 conflict
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 0x0e0471c0a2…02f681
Audit this contract →
← previous block·next block →recent activity