← previous blocknext block →recent activity
Analyzing
Block #90,918,294
13 transactions · 13 stateful · 2026-07-28 00:46:01 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,918,294 · 13 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
6w08w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebac0f82…a49c
0x34b655…2a6f
6 touches
3 conflicts
0x99701186…1cbf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x15437606…7ec8
0x34b655…2a6f
2 touches
0 conflicts
0x5e782d17…5318
0x34b655…2a6f
2 touches
0 conflicts
0x6254804c…a03c
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 0xebac0f82ec…86a49c
Audit this contract →
← previous block·next block →recent activity