← previous blocknext block →recent activity
Analyzing
Block #83,203,789
14 transactions · 11 stateful · 2026-06-23 16:20:32 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,203,789 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fde64da…aa3e
0x2a68ba…90c5
6 touches
3 conflicts
0x43f3aa6f…5482
0x851145…3f07
5 touches
3 conflicts
0x703b861a…cbe3
0x188d58…ea8e
4 touches
1 conflict
0x703b861a…cbe4
0x188d58…ea8e
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0xc03a03cd…fbcf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x0fde64da0b…a5aa3e
Audit this contract →
← previous block·next block →recent activity