← previous blocknext block →recent activity
Analyzing
Block #83,203,605
14 transactions · 13 stateful · 2026-06-23 16:19:18 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,203,605 · 14 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
1w02w03w14w25w16w27w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9021b63b…a6cd
0x40c49f…2af0
3 touches
1 conflict
0x3e7d6586…da7b
0x40c49f…2af0
3 touches
1 conflict
0x3596914f…81f1
0x40c49f…2af0
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