← previous blocknext block →recent activity
Analyzing
Block #82,327,747
13 transactions · 12 stateful · 2026-06-19 14:45:47 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,327,747 · 13 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
1w02w13w04w16w07w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x22d3c767…e4d1
0x34b655…2a6f
4 touches
1 conflict
0x476615f7…2aaf
0x34b655…2a6f
4 touches
1 conflict
0xd06fb4dc…5204
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x66c5e348…51d0
0xa6afd3…d132
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 0x15c9b5bf08…57f732
Audit this contract →
← previous block·next block →recent activity