← previous blocknext block →recent activity
Analyzing
Block #84,559,194
10 transactions · 9 stateful · 2026-06-29 23:00:52 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,559,194 · 10 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
1w02w14w06w17w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7e45018…b59c
0x34b655…2a6f
6 touches
3 conflicts
0x98d58911…19f2
0x34b655…2a6f
6 touches
3 conflicts
0xed660153…a905
0x34b655…2a6f
6 touches
3 conflicts
0x24227bc5…cb16
0x34b655…2a6f
4 touches
1 conflict
0x2c15adb7…e65d
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x56253387…ff0e
0x34b655…2a6f
4 touches
1 conflict
0x74888025…a5b8
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 0xa7e45018ba…2fb59c
Audit this contract →
← previous block·next block →recent activity