← previous blocknext block →recent activity
Analyzing
Block #83,942,834
18 transactions · 18 stateful · 2026-06-27 02:33:15 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,942,834 · 18 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
6w07w18w010w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x7c5260f4…bd96
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0x466ad8…6a98
2 touches
0 conflicts
0xb75581a8…a995
0x466ad8…6a98
2 touches
0 conflicts
0x28a0f3c1…a540
0x754704…b603
2 touches
0 conflicts
0x9a0f0914…fc7e
0x754704…b603
2 touches
0 conflicts
0xca155f57…521b
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity