← previous blocknext block →recent activity
Analyzing
Block #83,845,324
28 transactions · 24 stateful · 2026-06-26 15:43:09 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,845,324 · 28 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
1w02w07w19w010w112w216w220w021w122w223w324w425w526w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x18aed20c…48f3
0x000000…012a
8 touches
6 conflicts
0x00000000…0004
0xd5b70d…615b
8 touches
6 conflicts
0x00000000…0003
0xd5b70d…615b
8 touches
6 conflicts
0x00000000…0000
0xd5b70d…615b
8 touches
6 conflicts
0x7c403af1…31b1
0x3bd359…433a
8 touches
6 conflicts
0x12309510…0ac2
0x000000…012a
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity