← previous blocknext block →recent activity
Analyzing
Block #90,996,374
19 transactions · 16 stateful · 2026-07-28 07:19:05 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,996,374 · 19 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
1w03w06w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a6b3039…6a98
0x34b655…2a6f
4 touches
1 conflict
0x65f90aa4…c97f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3e4af36e…07ae
0x34b655…2a6f
4 touches
1 conflict
0x07d2d053…aa96
0x34b655…2a6f
2 touches
0 conflicts
0x0a9bc0b4…1191
0x34b655…2a6f
2 touches
0 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
2 touches
0 conflicts
0x1175233a…64e7
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 0x4a6b3039f4…046a98
Audit this contract →
← previous block·next block →recent activity