← previous blocknext block →recent activity
Analyzing
Block #86,132,903
26 transactions · 19 stateful · 2026-07-07 05:51:43 UTC
Parallelism
85/100
Blocked
21%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,132,903 · 26 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
1w09w113w014w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x3d7c2aae…4751
0x065c9d…c394
3 touches
1 conflict
0x449dde95…bb4c
0x065c9d…c394
3 touches
1 conflict
0x46cb45de…a567
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0000
0x2d82ac…5fd8
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity