← previous blocknext block →recent activity
Analyzing
Block #84,363,631
21 transactions · 21 stateful · 2026-06-29 01:16:33 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,363,631 · 21 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
1w02w13w04w19w012w213w014w217w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44843215…109b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf997c4c7…617d
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xd08b8a31…0998
0x34b655…2a6f
5 touches
3 conflicts
0x9f53ac8a…80d1
0xd32edf…ff58
5 touches
3 conflicts
0x5eeea918…8147
0x34b655…2a6f
4 touches
1 conflict
0x7fe97198…79ab
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 0x44843215c9…be109b
Audit this contract →
← previous block·next block →recent activity