← previous blocknext block →recent activity
Analyzing
Block #82,667,013
17 transactions · 12 stateful · 2026-06-21 04:32:38 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,667,013 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w18w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4c3ebba…f37e
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xef02ed46…48a4
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xc23dcce7…da7e
0x065c9d…c394
4 touches
1 conflict
0x915c095e…c1e5
0x69df8a…6292
2 touches
0 conflicts
0x5b4b3fa7…2f73
0x754704…b603
2 touches
0 conflicts
0xe42816b6…404e
0x754704…b603
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 0xd4c3ebbad3…8af37e
Audit this contract →
← previous block·next block →recent activity