← previous blocknext block →recent activity
Analyzing
Block #86,243,838
19 transactions · 17 stateful · 2026-07-07 18:12:25 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,243,838 · 19 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
2w03w14w25w06w17w09w110w213w314w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43e3decb…be40
0x34b655…2a6f
6 touches
3 conflicts
0x34443913…cbf3
0x336ed4…c59c
6 touches
3 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
6 touches
3 conflicts
0xd800e635…b1d7
0x34b655…2a6f
6 touches
3 conflicts
0x006e55b1…660f
0x8d1565…6723
6 touches
3 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 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 0x43e3decb93…7dbe40
Audit this contract →
← previous block·next block →recent activity