← previous blocknext block →recent activity
Analyzing
Block #83,455,139
16 transactions · 14 stateful · 2026-06-24 20:19:38 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,455,139 · 16 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
6w07w08w110w011w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b2dce58…2f1d
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe334a6b5…173c
0x34b655…2a6f
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0xe512d87d…c9ab
0x065c9d…c394
4 touches
1 conflict
0x665d85cc…0805
0x065c9d…c394
3 touches
1 conflict
0x2fa99ea3…a588
0x065c9d…c394
3 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 0x2b2dce5827…4f2f1d
Audit this contract →
← previous block·next block →recent activity