← previous blocknext block →recent activity
Analyzing
Block #86,243,985
31 transactions · 24 stateful · 2026-07-07 18:13:24 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,243,985 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w29w010w114w015w318w419w423w124w226w328w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
8 touches
6 conflicts
0xdfa159d0…1576
0x065c9d…c394
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xa678cb89…4abd
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
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: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity