← previous blocknext block →recent activity
Analyzing
Block #90,803,160
17 transactions · 14 stateful · 2026-07-27 15:06:41 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,803,160 · 17 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
5w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0xa9f8096f…f132
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x000a7fe4…fa7c
0x34b655…2a6f
2 touches
0 conflicts
0x0819f51e…4973
0x34b655…2a6f
2 touches
0 conflicts
0x19e69334…a345
0x34b655…2a6f
2 touches
0 conflicts
0x2d7b3d63…c856
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 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity