← previous blocknext block →recent activity
Analyzing
Block #87,356,908
10 transactions · 9 stateful · 2026-07-12 22:13:54 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,356,908 · 10 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
1w04w05w16w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0ce5883…746c
0x2a68ba…90c5
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xbde30d77…b032
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x284ae7ce…7917
0x851145…3f07
4 touches
1 conflict
0x3fcc24d4…fa74
0x851145…3f07
4 touches
1 conflict
0x6b76d7a1…d19b
0x851145…3f07
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: Kuru Exchange: MarginAccount
1 conflict on slot 0xb0ce5883f1…ea746c
Audit this contract →
← previous block·next block →recent activity