← previous blocknext block →recent activity
Analyzing
Block #86,104,453
35 transactions · 32 stateful · 2026-07-07 02:41:45 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.49
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,104,453 · 35 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
13w014w125w228w029w130w231w332w433w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
6 touches
3 conflicts
0x84fb2a36…db89
0x34b655…2a6f
5 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x3bdab090…c5bf
0x34b655…2a6f
4 touches
1 conflict
0x7b3f8378…b37d
0x34b655…2a6f
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity