← previous blocknext block →recent activity
Analyzing
Block #86,483,813
23 transactions · 18 stateful · 2026-07-08 20:55:44 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,483,813 · 23 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
2w03w14w28w010w011w112w213w317w118w019w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x66e6480e…c384
0x40c49f…2af0
6 touches
3 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0xebd8c9b0…2ba6
0x34b655…2a6f
4 touches
1 conflict
0x3c66b1a7…ca53
0x40c49f…2af0
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity