← previous blocknext block →recent activity
Analyzing
Block #83,356,197
17 transactions · 13 stateful · 2026-06-24 09:18:30 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.35
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,356,197 · 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
1w02w03w14w05w06w18w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5a38e46…a68c
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xfb4cb196…8c4a
0x34b655…2a6f
4 touches
1 conflict
0x64bd3fa9…ce3f
0x065c9d…c394
4 touches
1 conflict
0x7ba000e1…3632
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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
1 conflict on slot 0xe5a38e469a…0da68c
Audit this contract →
← previous block·next block →recent activity