← previous blocknext block →recent activity
Analyzing
Block #86,102,655
23 transactions · 19 stateful · 2026-07-07 02:29:47 UTC
Parallelism
87/100
Blocked
26%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,102,655 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w114w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc13f57e…786f
0x34b655…2a6f
6 touches
3 conflicts
0xc4cb048e…7562
0x34b655…2a6f
6 touches
3 conflicts
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x0d2a45c4…ae38
0xa6afd3…d132
3 touches
1 conflict
0xb5b71470…8bb8
0x754704…b603
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: Perpl
3 conflicts on slot 0xfc13f57e3b…d4786f
Audit this contract →
← previous block·next block →recent activity