← previous blocknext block →recent activity
Analyzing
Block #83,037,881
18 transactions · 15 stateful · 2026-06-22 21:51:08 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,037,881 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w39w210w211w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc68d6f14…bdde
0x34b655…2a6f
6 touches
3 conflicts
0x9fb55ee7…8ecc
0xa6afd3…d132
6 touches
3 conflicts
0xceb535f3…19cf
0x34b655…2a6f
6 touches
3 conflicts
0xd1ec379e…5e00
0x34b655…2a6f
4 touches
1 conflict
0xd7066173…e5bd
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
6 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity