← previous blocknext block →recent activity
Analyzing
Block #85,363,624
17 transactions · 13 stateful · 2026-07-03 16:24:23 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,363,624 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w16w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a1e6958…6dc3
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x6827c800…a1a1
0x34b655…2a6f
4 touches
1 conflict
0x56a919c4…ab49
0xad96c3…8d7c
4 touches
1 conflict
0x5948f6e6…42c4
0x01bff4…1071
2 touches
0 conflicts
0x78eb0de5…1db2
0x01bff4…1071
2 touches
0 conflicts
0xed67cadc…c62e
0x01bff4…1071
2 touches
0 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: Uniswap: PoolManager
1 conflict on slot 0x3a1e695869…4c6dc3
Audit this contract →
← previous block·next block →recent activity