← previous blocknext block →recent activity
Analyzing
Block #90,117,732
9 transactions · 8 stateful · 2026-07-25 05:22:23 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,117,732 · 9 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
1w02w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8834cf3…0004
0x34b655…2a6f
4 touches
1 conflict
0xda0b544d…0d92
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf346808d…6ad4
0x34b655…2a6f
4 touches
1 conflict
0xfb95f8cc…4025
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x38d7a7f4…ffe6
0x34b655…2a6f
4 touches
1 conflict
0x6f3ece6e…c36f
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
1 conflict on slot 0xd8834cf34a…0d0004
Audit this contract →
← previous block·next block →recent activity