← previous blocknext block →recent activity
Analyzing
Block #83,193,313
20 transactions · 16 stateful · 2026-06-23 15:10:25 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,193,313 · 20 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
5w06w08w19w211w317w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0xb1acfe51…c6b1
0x3bd359…433a
2 touches
0 conflicts
0x08b8e539…b9f9
0x754704…b603
2 touches
0 conflicts
0xa1087a5c…66c4
0x754704…b603
2 touches
0 conflicts
0xd2582e55…3ca4
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: 0x40c49f17…d22af0
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity