← previous blocknext block →recent activity
Analyzing
Block #86,354,139
16 transactions · 13 stateful · 2026-07-08 06:28:56 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,354,139 · 16 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
2w03w16w010w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83f08cad…bcc7
0x34b655…2a6f
4 touches
1 conflict
0x83f08cad…bcc8
0x34b655…2a6f
4 touches
1 conflict
0x8e1bab55…9a5e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xd7bbf766…43f0
0x34b655…2a6f
4 touches
1 conflict
0xe6f4f023…6469
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x15e66c55…5429
0x34b655…2a6f
3 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
1 conflict on slot 0x83f08cad3b…acbcc7
Audit this contract →
← previous block·next block →recent activity