← previous blocknext block →recent activity
Analyzing
Block #83,578,380
17 transactions · 14 stateful · 2026-06-25 10:01:35 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,578,380 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x4cd6928f…1a19
0x2a68ba…90c5
4 touches
1 conflict
0x63e99741…626e
0xa6afd3…d132
4 touches
1 conflict
0x9cf5ac50…1be9
0xa6afd3…d132
4 touches
1 conflict
0x0026a9d8…9665
0xa6afd3…d132
3 touches
1 conflict
0x89ae6b35…a5f8
0xa6afd3…d132
3 touches
1 conflict
0xcd621226…2df8
0x368ee5…7ca4
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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
1 conflict on slot 0xd8dd03ce37…9cdc8d
Audit this contract →
← previous block·next block →recent activity