← previous blocknext block →recent activity
Analyzing
Block #90,994,536
11 transactions · 11 stateful · 2026-07-28 07:09:44 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,994,536 · 11 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
2w03w14w05w27w09w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x65f90aa4…c97f
0x34b655…2a6f
6 touches
3 conflicts
0x3e4af36e…07ae
0x34b655…2a6f
6 touches
3 conflicts
0xff3d6184…43dd
0x34b655…2a6f
6 touches
3 conflicts
0x363f99e4…32c8
0x34b655…2a6f
4 touches
1 conflict
0x4a6b3039…6a98
0x34b655…2a6f
4 touches
1 conflict
0x4b2d7d8d…c5b9
0x34b655…2a6f
4 touches
1 conflict
0x5d7273be…cd68
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity