← previous blocknext block →recent activity
Analyzing
Block #90,287,715
21 transactions · 20 stateful · 2026-07-25 19:39:50 UTC
Parallelism
90/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,287,715 · 21 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
1w02w19w010w111w012w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44571ed8…6022
0x34b655…2a6f
4 touches
1 conflict
0x4bc1abab…5874
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd19c9d38…b459
0x34b655…2a6f
4 touches
1 conflict
0xe4d8276f…32e9
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x44571ed817…cd6022
Audit this contract →
← previous block·next block →recent activity