← previous blocknext block →recent activity
Analyzing
Block #90,797,352
23 transactions · 17 stateful · 2026-07-27 14:37:27 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.3
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,797,352 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w09w111w012w114w217w318w421w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x510c8ae3…eb30
0x34b655…2a6f
4 touches
1 conflict
0x5f56ffe5…09c0
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0xe8d8a9a2…40f3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
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 0x510c8ae3e4…9feb30
Audit this contract →
← previous block·next block →recent activity