← previous blocknext block →recent activity
Analyzing
Block #90,794,102
22 transactions · 18 stateful · 2026-07-27 14:21:06 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,794,102 · 22 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
1w02w13w14w09w010w111w214w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x1435fd06…60ea
0x34b655…2a6f
4 touches
1 conflict
0x3a2a8323…3f40
0x34b655…2a6f
4 touches
1 conflict
0xacfd8774…87ec
0x34b655…2a6f
4 touches
1 conflict
0xc516fef7…841c
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity