← previous blocknext block →recent activity
Analyzing
Block #86,455,322
10 transactions · 7 stateful · 2026-07-08 17:45:00 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,455,322 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0xe944b4f1…3445
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x37d710c8…45c1
0x34b655…2a6f
4 touches
1 conflict
0x4c169e7f…3c6c
0x40c49f…2af0
2 touches
0 conflicts
0xcd790d53…da37
0x40c49f…2af0
2 touches
0 conflicts
0x2f74f175…9284
0x69df8a…6292
2 touches
0 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
1 conflict on slot 0x85eb131679…60bb9e
Audit this contract →
← previous block·next block →recent activity