← previous blocknext block →recent activity
Analyzing
Block #83,637,789
18 transactions · 17 stateful · 2026-06-25 16:38:25 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,637,789 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w112w015w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd08b8a31…0998
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7e17e82a…9748
0x34b655…2a6f
4 touches
1 conflict
0x94dc8af7…ec26
0x34b655…2a6f
4 touches
1 conflict
0x9749bf7d…fdfe
0x34b655…2a6f
4 touches
1 conflict
0xa79fea8c…0178
0x34b655…2a6f
4 touches
1 conflict
0xb1c67a7d…b9b1
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xd08b8a315e…ef0998
Audit this contract →
← previous block·next block →recent activity