← previous blocknext block →recent activity
Analyzing
Block #83,759,410
29 transactions · 26 stateful · 2026-06-26 06:09:46 UTC
Parallelism
79/100
Blocked
54%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,759,410 · 29 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
2w03w04w17w28w39w410w112w013w114w215w316w417w518w520w225w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
10 touches
10 conflicts
0x2484cc15…5afc
0x34b655…2a6f
10 touches
10 conflicts
0x5941ac48…c525
0x34b655…2a6f
10 touches
10 conflicts
0x225d5b28…a7e5
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x8190162b…5c4b
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity