← previous blocknext block →recent activity
Analyzing
Block #82,538,253
23 transactions · 14 stateful · 2026-06-20 14:09:59 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,538,253 · 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
2w03w14w06w17w213w014w116w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b305a3b…1c35
0x34b655…2a6f
8 touches
6 conflicts
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0bdb2472…4488
0x065c9d…c394
4 touches
1 conflict
0x378438ab…8652
0x065c9d…c394
3 touches
1 conflict
0x4d4aece1…31f3
0x065c9d…c394
3 touches
1 conflict
0xefb673ff…92cd
0x065c9d…c394
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
6 conflicts on slot 0x8b305a3b6b…0c1c35
Audit this contract →
← previous block·next block →recent activity