← previous blocknext block →recent activity
Analyzing
Block #90,514,347
14 transactions · 14 stateful · 2026-07-26 14:53:46 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,514,347 · 14 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
1w02w15w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabd0bcfc…64e2
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x4bd79f91…4d5b
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x183f02d9…7bef
0x34b655…2a6f
2 touches
0 conflicts
0x29ca0976…f499
0x34b655…2a6f
2 touches
0 conflicts
0x3076192f…07b1
0x34b655…2a6f
2 touches
0 conflicts
0x34a2c248…f7ed
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 0xabd0bcfc80…a364e2
Audit this contract →
← previous block·next block →recent activity