← previous blocknext block →recent activity
Analyzing
Block #90,223,986
15 transactions · 15 stateful · 2026-07-25 14:18:04 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,223,986 · 15 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
2w03w14w05w16w28w312w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08024b2c…d265
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x349f436e…80e6
0x34b655…2a6f
4 touches
1 conflict
0x481b500f…7ef3
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7ac265cd…0253
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
6 conflicts on slot 0x08024b2c16…37d265
Audit this contract →
← previous block·next block →recent activity