← previous blocknext block →recent activity
Analyzing
Block #85,827,021
19 transactions · 18 stateful · 2026-07-05 19:51:13 UTC
Parallelism
63/100
Blocked
39%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,827,021 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w26w37w48w59w613w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa164d951…1534
0xe1c8b7…3022
14 touches
21 conflicts
0x44ed742f…63f5
0x3bd359…433a
14 touches
21 conflicts
0x4eb758b8…b13b
0x3bd359…433a
14 touches
21 conflicts
0x67d846dd…358c
0xc5db38…7777
8 touches
6 conflicts
0x12a9b76e…cb76
0x3bd359…433a
8 touches
6 conflicts
0x7cf5136f…ba69
0x9f3832…4ae4
8 touches
6 conflicts
0xb5681747…c048
0xe1c8b7…3022
8 touches
6 conflicts
0x9527c4ff…73fb
0xc5db38…7777
8 touches
6 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: 0xe1c8b733…e33022
21 conflicts on slot 0xa164d95170…fa1534
Audit this contract →
← previous block·next block →recent activity