← previous blocknext block →recent activity
Analyzing
Block #90,812,896
14 transactions · 14 stateful · 2026-07-27 15:55:45 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,812,896 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefeb7be7…ae9a
0x34b655…2a6f
4 touches
1 conflict
0xa46242d8…c0a7
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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 0xefeb7be71c…27ae9a
Audit this contract →
← previous block·next block →recent activity