← previous blocknext block →recent activity
Analyzing
Block #83,624,240
27 transactions · 24 stateful · 2026-06-25 15:07:53 UTC
Parallelism
85/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,624,240 · 27 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
4w05w110w011w112w215w018w020w223w124w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xef3a4217…dec8
0x34b655…2a6f
6 touches
3 conflicts
0xaa6f28d9…83ef
0x34b655…2a6f
4 touches
2 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x3671c46b…ae92
0x34b655…2a6f
4 touches
1 conflict
0x5a5dd7b4…fba4
0x34b655…2a6f
4 touches
1 conflict
0x7534f53d…6ed4
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity