← previous blocknext block →recent activity
Analyzing
Block #90,791,108
27 transactions · 23 stateful · 2026-07-27 14:06:03 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,791,108 · 27 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
2w03w15w06w17w210w011w112w213w114w215w016w118w219w325w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x007892de…5752
0x34b655…2a6f
4 touches
1 conflict
0x04ccf840…d0b7
0x34b655…2a6f
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x252771a6…3918
0x34b655…2a6f
4 touches
1 conflict
0x4a830181…d1df
0x34b655…2a6f
4 touches
1 conflict
0x5a100ac0…96d3
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: 0x48cba278…e2b48b
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity