← previous blocknext block →recent activity
Analyzing
Block #90,810,605
12 transactions · 11 stateful · 2026-07-27 15:44:11 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,810,605 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w18w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf50ebbf7…73c8
0x34b655…2a6f
4 touches
1 conflict
0xa9028fac…3d0f
0x34b655…2a6f
4 touches
1 conflict
0xbd6941a1…6281
0x34b655…2a6f
4 touches
1 conflict
0xc6b9bb4b…145a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0x0e04c4cc…551a
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 0xf50ebbf717…e873c8
Audit this contract →
← previous block·next block →recent activity