← previous blocknext block →recent activity
Analyzing
Block #90,682,380
7 transactions · 7 stateful · 2026-07-27 04:59:04 UTC
Parallelism
43/100
Blocked
43%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,682,380 · 7 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
2w03w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x551c5873…e0bc
0x34b655…2a6f
4 touches
1 conflict
0x7032dc14…49ea
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
0x278686dc…698d
0x34b655…2a6f
4 touches
1 conflict
0x364026a6…1715
0x34b655…2a6f
4 touches
1 conflict
0x0db81afb…5c06
0x34b655…2a6f
2 touches
0 conflicts
0x14ea9ada…e627
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 0x551c5873fe…5ae0bc
Audit this contract →
← previous block·next block →recent activity