← previous blocknext block →recent activity
Analyzing
Block #87,920,027
30 transactions · 22 stateful · 2026-07-15 13:01:02 UTC
Parallelism
87/100
Blocked
41%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,920,027 · 30 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
1w02w03w14w18w09w110w011w117w021w123w124w226w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0xd64abf23…9002
0x065c9d…c394
4 touches
1 conflict
0x051aa260…b0a4
0x34b655…2a6f
4 touches
1 conflict
0x13f8c55c…3061
0x34b655…2a6f
4 touches
1 conflict
0x2a88784d…f1be
0x34b655…2a6f
4 touches
1 conflict
0x364289f7…f98a
0x34b655…2a6f
4 touches
1 conflict
0x4797cebc…5c38
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity